Triple
T481648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1967 Triple Crown |
E9180
|
entity |
| Predicate | winnerBats |
P14864
|
FINISHED |
| Object | left |
—
|
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: left | Statement: [1967 Triple Crown, winnerBats, left]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: winnerBats Context triple: [1967 Triple Crown, winnerBats, left]
-
A.
notableBatter
Indicates that the subject is a batter who is particularly prominent, distinguished, or noteworthy in the context of batting.
-
B.
winningTeam
Indicates which team is the victor in a given competition, game, or contest.
-
C.
winnerPlaysIn
Indicates that the entity identified as the winner of a contest or match participates in a subsequent game, round, or event.
-
D.
winnerCount
Indicates the number of entities that are designated as winners in a given context or event.
-
E.
decisiveGameBatter
Indicates that a batter participated in a game situation that was decisive in determining the final outcome of the contest.
- 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_69a2e7ff81708190b0507a24a997232c |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f05a7f6c819082b4a5a3e69468a6 |
completed | Feb. 28, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69a2edf321288190b5d560f75782c2cb |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2ef4030608190b39852b347a505ca |
completed | Feb. 28, 2026, 1:36 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.