Triple
T2191358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boston University Terriers football team |
E49867
|
entity |
| Predicate | terminationYear |
P214
|
FINISHED |
| Object | 1997 |
—
|
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: 1997 | Statement: [Boston University Terriers football team, terminationYear, 1997]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminationYear Context triple: [Boston University Terriers football team, terminationYear, 1997]
-
A.
endYear
chosen
Indicates the year in which an event, state, or relationship comes to an end.
-
B.
closureYear
Indicates the year in which an entity (such as an organization, facility, or service) ceased operations or was officially closed.
-
C.
serializationEndYear
Indicates the year in which the serialization or serialized publication of an entity concluded.
-
D.
separationYear
Indicates the year in which two entities ended or dissolved their relationship or association.
-
E.
activeYearsEndTime
Indicates the point in time when an entity’s period of activity or operation comes to an end.
- 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_69a88aaba3c48190b351cab9b26989ff |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbf3f5e008190beda3ce5d77209e0 |
completed | March 7, 2026, 6:01 a.m. |
| PD | Predicate disambiguation | batch_69abbda52328819089c7ab111bebb0ca |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.