Triple
T16199235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daytona 200 |
E393151
|
entity |
| Predicate | formerClass |
P30139
|
FINISHED |
| Object | premier Grand Prix-style motorcycles |
—
|
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: premier Grand Prix-style motorcycles | Statement: [Daytona 200, formerClass, premier Grand Prix-style motorcycles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerClass Context triple: [Daytona 200, formerClass, premier Grand Prix-style motorcycles]
-
A.
formerType
Indicates that one entity previously had a certain type, role, or classification but no longer does.
-
B.
formerCategory
chosen
Indicates that an entity previously belonged to a given category but no longer does.
-
C.
formerFunction
Indicates that an entity previously held a specific role, position, or function but no longer does so.
-
D.
predecessorClass
Indicates that one class precedes another in an ordered sequence or hierarchy, typically representing an earlier version or prior stage of that class.
-
E.
formerPart
Indicates that an entity was once a component or member of another entity but is no longer part of it.
- 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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e222de2db481908471b9c73d444607 |
completed | April 17, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69e219e11f6081909106b1240a17fd37 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.