Triple
T13426483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rally Mexico |
E313493
|
entity |
| Predicate | specialStageType |
P108749
|
FINISHED |
| Object | super special stage |
—
|
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: super special stage | Statement: [Rally Mexico, specialStageType, super special stage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specialStageType Context triple: [Rally Mexico, specialStageType, super special stage]
-
A.
hasSuperSpecialStage
chosen
Indicates that an entity is associated with or includes a particularly exceptional or designated “super special” stage within a process, lifecycle, or sequence.
-
B.
specialAppearance
Indicates that an entity makes a notable or exceptional appearance distinct from its usual or regular presence.
-
C.
usesStageType
Indicates that one entity employs or operates with a particular type or category of stage.
-
D.
coreStageType
Indicates the specific kind or classification of a core stage within a larger process, system, or lifecycle.
-
E.
superStageStructure
Indicates that one stage structure functions as a higher-level or encompassing structure relative to another stage structure within a staged process 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_69d806ad0c44819088833ae1ec9e9690 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaed1f9208190bf5ef5b8a7ded376 |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03926188190ab3948d1f5d3941f |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:40 p.m.