Triple
T4329871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Preakness Stakes |
E96720
|
entity |
| Predicate | permanentReturnToPimlico |
P55594
|
FINISHED |
| Object | 1909 |
—
|
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: 1909 | Statement: [Preakness Stakes, permanentReturnToPimlico, 1909]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: permanentReturnToPimlico Context triple: [Preakness Stakes, permanentReturnToPimlico, 1909]
-
A.
secretariat
Indicates that an entity serves as an administrative office or coordinating body (a secretariat) responsible for managing and supporting the activities of an organization or group.
-
B.
hasRacecourse
Indicates that an entity possesses, contains, or is associated with a racecourse facility or track.
-
C.
returnedFromRetirement
Indicates that an entity has resumed an activity, role, or position after having previously retired from it.
-
D.
raceMeeting
Indicates a competitive event where multiple participants race against each other under shared rules and conditions.
-
E.
managedPennantWinner
Indicates that a person served as the manager of a team during a season in which that team won the league pennant.
- 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_69b34542fd908190b11b08faad8decfd |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3513545fc81909e29de7eae1829f7 |
completed | March 12, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69b34f4e13fc8190a42c519f37959d27 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b34ff654308190b9717526120d80d3 |
completed | March 12, 2026, 11:44 p.m. |
Created at: March 12, 2026, 11:13 p.m.