Triple
T35564155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2015 Daytona 500 |
E1027720
|
entity |
| Predicate | lapsInStageFormat |
P181496
|
FINISHED |
| Object | pre-stage-era |
—
|
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: pre-stage-era | Statement: [2015 Daytona 500, lapsInStageFormat, pre-stage-era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lapsInStageFormat Context triple: [2015 Daytona 500, lapsInStageFormat, pre-stage-era]
-
A.
lapsStage
Indicates that one entity completes or covers a specified stage or segment of a course or track, typically as part of a multi-stage or lap-based progression.
-
B.
hasLapStructure
Indicates that an entity possesses a lap-like structural configuration or component as part of its overall form or design.
-
C.
numberOfStages
Indicates the total count of distinct stages or phases associated with a given process, event, or entity.
-
D.
lapsOrTimeBased
chosen
Indicates a relationship where a quantity or condition is defined either in terms of completed laps or elapsed time, treating these two measures as interchangeable criteria.
-
E.
numberPerStage
Indicates the quantity or count associated with each distinct stage in a multi-stage process or sequence.
- 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_69f76e020fd8819081cb080e7e203083 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79a54aa3c8190b2bb5d790b2d42d4 |
completed | May 3, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69f7961970408190b669cc556e30a608 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.