Triple
T4349525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tattenham Corner |
E97986
|
entity |
| Predicate | importanceInRacing |
P55676
|
FINISHED |
| Object | key tactical point in The Derby |
—
|
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: key tactical point in The Derby | Statement: [Tattenham Corner, importanceInRacing, key tactical point in The Derby]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: importanceInRacing Context triple: [Tattenham Corner, importanceInRacing, key tactical point in The Derby]
-
A.
importanceInCycling
Indicates the degree to which something is considered significant, influential, or central within the context of cycling.
-
B.
raceWins
Indicates that one participant wins or finishes ahead of another in a race or competitive event.
-
C.
racingSeries
Indicates that one entity is a racing series in which the other entity (such as a race, team, or driver) participates or to which it belongs.
-
D.
positionOnRace
Indicates the relative ranking or placement an entity holds within the context of a race or competitive event.
-
E.
timingOfRace
Indicates the temporal details or schedule associated with a race, such as its start time, duration, or overall timing.
- 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_69b3454965f881908c41190bb22f0e4b |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351a840248190b88c8a7be9158d25 |
completed | March 12, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69b34f51ed7c8190b7bf5f44b56b730d |
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:15 p.m.