Triple
T34502653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trinity College Foundation Studies |
E885797
|
entity |
| Predicate | offersIntakeType |
P56389
|
FINISHED |
| Object | standard intake |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: standard intake | Statement: [Trinity College Foundation Studies, offersIntakeType, standard intake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersIntakeType Context triple: [Trinity College Foundation Studies, offersIntakeType, standard intake]
-
A.
offersEnrollmentType
chosen
Indicates that an entity provides or makes available a specific type or category of enrollment option.
-
B.
offeringType
Indicates the category or nature of what is being offered in a transaction or interaction (e.g., product, service, or other type of offering).
-
C.
offersForm
Indicates that one entity provides or makes available a specific form (e.g., a document or interface) for another entity to use or complete.
-
D.
offersServiceType
Indicates that one entity provides or makes available a specific type or category of service to another entity or the public.
-
E.
offersPanelType
Indicates that an entity provides or makes available a specific type of panel as part of its offerings.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fde9fc184c8190bebef35df0e76076 |
completed | May 8, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69fde6e5beb4819094945a695e961d88 |
completed | May 8, 2026, 1:36 p.m. |
Created at: May 1, 2026, 2:01 a.m.