Triple
T22401330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1982 World 600 |
E553767
|
entity |
| Predicate | leadChanges |
P148013
|
FINISHED |
| Object | 47 |
—
|
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: 47 | Statement: [1982 World 600, leadChanges, 47]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadChanges Context triple: [1982 World 600, leadChanges, 47]
-
A.
leadingOrgan
Indicates that one entity serves as the primary or most responsible organizing body or authority for another entity or activity.
-
B.
helpsLead
Indicates that one entity assists or contributes to another entity’s act of leading or guiding.
-
C.
leader2
Indicates that one entity serves as a leader, chief, or primary authority figure in relation to another entity.
-
D.
leadSingle
Indicates that an entity serves as the primary or featured performer, contributor, or focus in a single work or instance.
-
E.
leadShip
Indicates that one entity serves as the commander or person in charge of a ship belonging to or associated with another entity.
- 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_69e11e4da7048190b4387d422a9a0de5 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f158b4a96c8190838f5dda21c4d853 |
completed | April 29, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69e8989495bc81909d2699fce5992e28 |
completed | April 22, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69e8aa39e3388190b659d59948ebf3e6 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:46 p.m.