Triple
T18134885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seattle Slew |
E434109
|
entity |
| Predicate | undefeatedThrough |
P63159
|
FINISHED |
| Object | 1977 Triple Crown series |
—
|
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: 1977 Triple Crown series | Statement: [Seattle Slew, undefeatedThrough, 1977 Triple Crown series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: undefeatedThrough Context triple: [Seattle Slew, undefeatedThrough, 1977 Triple Crown series]
-
A.
isUndefeated
chosen
Indicates that an entity has not been defeated in any relevant contest, match, or competition.
-
B.
unbeatenStreakLength
Indicates the length of a continuous sequence during which an entity has not been defeated or has remained without a loss.
-
C.
undefeatedTeamInFinal
Indicates that a team reached the final match of a competition and did so without having lost any game up to and including that final.
-
D.
defeatedBy
Indicates that one entity has been beaten, overcome, or conquered by another in a contest, conflict, or competition.
-
E.
undefeatedInProfessionalBoxing
Indicates that a boxer has never lost any match in their professional boxing career.
- 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_69d8b909e8cc81908df4cc2b8ea6d11f |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4de055c608190a090c2737904e5f9 |
completed | April 19, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69e43317d11c81908d1dc14921566b47 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:29 a.m.