Triple
T24791767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daytona Prototype international |
E620268
|
entity |
| Predicate | competitionClassName |
P10053
|
FINISHED |
| Object | Prototype (P) class |
—
|
NE NERFINISHED |
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: Prototype (P) class | Statement: [Daytona Prototype international, competitionClassName, Prototype (P) class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competitionClassName Context triple: [Daytona Prototype international, competitionClassName, Prototype (P) class]
-
A.
competitionClass
chosen
Indicates that one entity is classified into a particular competitive category or level within a competition or contest.
-
B.
competitionTitle
Indicates the official name or title assigned to a specific competition or contest.
-
C.
competitionRenamedAs
Indicates that a competition previously known by one name is now officially referred to by a different name.
-
D.
typeOfCompetition
Indicates the specific kind or category of competition in which an entity participates or is involved.
-
E.
competitionDepicted
Indicates that a competitive event or rivalry between entities is shown or represented in some medium or context.
- 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_69e2fabe77c8819085f7ce6486248139 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
Created at: April 18, 2026, 4:47 a.m.