Triple
T35730206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Cutting |
E1032729
|
entity |
| Predicate | comesBeforeOnLap |
P184081
|
FINISHED |
| Object | Reid Park |
—
|
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: Reid Park | Statement: [The Cutting, comesBeforeOnLap, Reid Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: comesBeforeOnLap Context triple: [The Cutting, comesBeforeOnLap, Reid Park]
-
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.
heldBefore
Indicates that one entity possessed or maintained control of something at an earlier time than another entity or event.
-
D.
hasLapStructure
Indicates that an entity possesses a lap-like structural configuration or component as part of its overall form or design.
-
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_69f76e10e59081908d81ad9ce22f40b6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aaabb58c8190bf81673608ecfb6e |
completed | May 3, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f7aa6795f481908940838ee7041ff5 |
completed | May 3, 2026, 8:04 p.m. |
Created at: May 3, 2026, 4:05 p.m.