Triple
T27005697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1985 New York Mets season |
E680234
|
entity |
| Predicate | divisionLeader |
P163084
|
FINISHED |
| Object | St. Louis Cardinals |
—
|
NE NERFINISHED |
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: St. Louis Cardinals | Statement: [1985 New York Mets season, divisionLeader, St. Louis Cardinals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: divisionLeader Context triple: [1985 New York Mets season, divisionLeader, St. Louis Cardinals]
-
A.
designatedLeader
Indicates that one entity has been formally chosen or assigned to serve as the leader of another entity or group.
-
B.
leader2
Indicates that one entity serves as a leader, chief, or primary authority figure in relation to another entity.
-
C.
leaderFrom
Indicates that an entity serves or has served as a leader originating from, representing, or associated with a specified place or organization.
-
D.
divisionTitle
Indicates the formal name or title assigned to a specific division within a larger organization or structure.
-
E.
leaderOfGroup
Indicates that an entity holds a leadership role or primary authority over a particular group.
- F. None of above. chosen
Provenance (4 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_69eeeb53939c8190bd431f32b060f01f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f63639a84c81909d700a539b458b42 |
completed | May 2, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69f631850ae08190a0ba51e4f1e4ccb3 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6352df6148190bc10772cd40bd7b3 |
completed | May 2, 2026, 5:32 p.m. |
Created at: April 27, 2026, 7 a.m.