Triple
T7219862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ladas |
E150228
|
entity |
| Predicate | finishedPositionInRace |
P55492
|
FINISHED |
| Object | second in the St Leger Stakes |
—
|
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: second in the St Leger Stakes | Statement: [Ladas, finishedPositionInRace, second in the St Leger Stakes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finishedPositionInRace Context triple: [Ladas, finishedPositionInRace, second in the St Leger Stakes]
-
A.
positionOnRace
Indicates the relative ranking or placement an entity holds within the context of a race or competitive event.
-
B.
finishPosition
chosen
Indicates the final rank or place an entity achieves in an ordered outcome, such as a race, competition, or sequence of results.
-
C.
raceWon
Indicates that one participant has achieved victory in a race or competitive event over others.
-
D.
timingOfRace
Indicates the temporal details or schedule associated with a race, such as its start time, duration, or overall timing.
-
E.
partOfRaceCourseSince
Indicates that an entity has been included as a component or segment of a race course starting from a specified point in time.
- 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_69c687effb44819092b95d07d0368c9f |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6e9b1a7908190bd215ffb84592e32 |
completed | March 27, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69c6e75f84e481909e7866186ae80cff |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:53 p.m.