Triple
T1073115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hippodrome of Olympia |
E23373
|
entity |
| Predicate | raceTypesHeld |
P19146
|
FINISHED |
| Object | tethrippon (four-horse chariot race) |
—
|
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: tethrippon (four-horse chariot race) | Statement: [Hippodrome of Olympia, raceTypesHeld, tethrippon (four-horse chariot race)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raceTypesHeld Context triple: [Hippodrome of Olympia, raceTypesHeld, tethrippon (four-horse chariot race)]
-
A.
raceMeeting
Indicates a competitive event where multiple participants race against each other under shared rules and conditions.
-
B.
raceCategory
Indicates the classification of an entity into a specific race or racial group within a defined categorization system.
-
C.
raceDayIncludes
chosen
Indicates that a particular race day schedule or event set contains or encompasses a specific race or racing-related activity.
-
D.
hasRacecourse
Indicates that an entity possesses, contains, or is associated with a racecourse facility or track.
-
E.
sportEventType
Indicates the specific kind or category of sport associated with a given sporting event.
- 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_69a493ee1f908190992b5f0d1b04459b |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b92afad88190b7705923f71fc760 |
completed | March 1, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69a4b73844708190a16c9e9824ca2fb6 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.