Triple
T35730205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Cutting |
E1032729
|
entity |
| Predicate | comesAfterOnLap |
P182965
|
FINISHED |
| Object | Griffins Bend |
—
|
NE NERFINISHED |
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: Griffins Bend | Statement: [The Cutting, comesAfterOnLap, Griffins Bend]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: comesAfterOnLap Context triple: [The Cutting, comesAfterOnLap, Griffins Bend]
-
A.
positionOnLap
Indicates that one entity is physically situated resting on the lap area of another entity.
-
B.
scheduledLaps
Indicates that a specific number or set of laps has been planned or assigned for an entity within a schedule or event.
-
C.
finishedSecondInRace
Indicates that an entity completed a race in second place relative to other competitors.
-
D.
arisesAfter
chosen
Indicates that one event, state, or condition comes into existence or begins only after another specified event, state, or condition has occurred.
-
E.
lapsCompleted
Indicates that an entity has finished a specified number of laps in a repeated circuit or course.
- 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_69f76e10e59081908d81ad9ce22f40b6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:05 p.m.