Triple
T16145772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daytona Beach Road Course |
E391776
|
entity |
| Predicate | usedBeachSection |
P74527
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Daytona Beach Road Course, usedBeachSection, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedBeachSection Context triple: [Daytona Beach Road Course, usedBeachSection, true]
-
A.
hasBeachUse
chosen
Indicates that an entity is used for, designated for, or associated with beach-related activities or purposes.
-
B.
hasBeachSection
Indicates that an area, location, or property includes or is associated with a specific section designated as a beach.
-
C.
beachSectorSupported
Indicates that a particular beach sector is maintained, serviced, or otherwise operationally supported by a responsible party or system.
-
D.
locatedAtEndOfBeach
Indicates that something is positioned at the far end or terminal point of a beach relative to a reference direction or area.
-
E.
beachSubdivisionOf
Indicates that a beach is a component or sub-area of a larger geographic or administrative region.
- 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_69d87f1c65e48190aa2b4c472e9bafc4 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21d9376fc8190bd9ef586b00c1d3b |
completed | April 17, 2026, 11:46 a.m. |
| PD | Predicate disambiguation | batch_69e182885bc08190822ae7e8a4b8ac1f |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5:01 a.m.