Triple
T23123506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Formula Ford |
E576961
|
entity |
| Predicate | raceStartFormat |
P30569
|
FINISHED |
| Object | standing start in many series |
—
|
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: standing start in many series | Statement: [Formula Ford, raceStartFormat, standing start in many series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raceStartFormat Context triple: [Formula Ford, raceStartFormat, standing start in many series]
-
A.
raceStartType
chosen
Indicates the manner or format in which a race is initiated (e.g., type or method of starting the race).
-
B.
raceRecordStarts
Indicates that a race record begins or is initiated at a specific point or event in time.
-
C.
raceAdded
Indicates that a race event or race-related record has been newly created or incorporated into a system or dataset.
-
D.
timingOfRace
Indicates the temporal details or schedule associated with a race, such as its start time, duration, or overall timing.
-
E.
raceTrack
Indicates that one entity serves as a race track or racing course used by another entity for racing activities.
- 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_69e245f6c2e881909a228fdcfeb7c7d3 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e5299c08190a578102cf2ff7080 |
completed | April 29, 2026, 4:51 a.m. |
| PD | Predicate disambiguation | batch_69ef89f020588190b43393e048e7eda3 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 3:59 p.m.