Triple
T16145708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daytona Rising |
E391774
|
entity |
| Predicate | addedFeature |
P82895
|
FINISHED |
| Object | wider concourses |
—
|
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: wider concourses | Statement: [Daytona Rising, addedFeature, wider concourses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addedFeature Context triple: [Daytona Rising, addedFeature, wider concourses]
-
A.
featureAdded
chosen
Indicates that a new feature has been introduced or incorporated into a system, product, or entity.
-
B.
createdFeature
Indicates that one entity brought another entity into existence or caused it to be produced as a feature.
-
C.
addedFor
Indicates that one entity was created, included, or introduced specifically for the benefit, use, or purpose of another entity.
-
D.
laterFeature
Indicates that one feature, event, or element occurs or is introduced after another in time.
-
E.
addedStructure
Indicates that one entity has introduced or incorporated an additional structural element into another entity or system.
- 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.