Triple
T17171817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Modern Baseball Committee |
E416752
|
entity |
| Predicate | focusesOnEraEnd |
P76220
|
FINISHED |
| Object | 1987 |
—
|
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: 1987 | Statement: [Modern Baseball Committee, focusesOnEraEnd, 1987]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusesOnEraEnd Context triple: [Modern Baseball Committee, focusesOnEraEnd, 1987]
-
A.
endedEra
Indicates that one entity brought about or marked the conclusion of a particular era associated with another entity.
-
B.
singleMatchEraEnd
Indicates the point in time when a particular single-match period or era concludes.
-
C.
followsEra
Indicates that one time period or era comes directly after another in chronological order.
-
D.
chronologyEnd
chosen
Indicates that one event, state, or time interval marks the ending point or conclusion of another in a temporal sequence.
-
E.
historicalEraUsheredIn
Indicates the historical era or period that was initiated or brought about as a result of a particular event, action, or entity.
- 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_69d886d5f34c8190b24564dfaa63f3fb |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3fc0ac22481909e992bb3a6ba36ad |
completed | April 18, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e3830d2a90819092386717dc56f0e8 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:37 a.m.