Triple
T38464564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nitros Oxide |
E912530
|
entity |
| Predicate | unlockableIn |
P191161
|
FINISHED |
| Object | Crash Team Racing Nitro-Fueled |
—
|
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: Crash Team Racing Nitro-Fueled | Statement: [Nitros Oxide, unlockableIn, Crash Team Racing Nitro-Fueled]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unlockableIn Context triple: [Nitros Oxide, unlockableIn, Crash Team Racing Nitro-Fueled]
-
A.
unlockable
Indicates that an entity can be opened or made accessible, typically by using a key, code, or other authorized method.
-
B.
canUnlock
Indicates that one entity has the ability or permission to unlock another entity.
-
C.
hasUnlockableStatusInSomeRegions
Indicates that the subject is restricted or locked in certain regions but can be made available or unlocked there under specific conditions.
-
D.
notAccessibleBy
Indicates that one entity cannot be reached, used, or obtained through another specified entity or means.
-
E.
unlockType
Indicates the method or condition by which access to something is unlocked or made available.
- F. None of above. chosen
Provenance (4 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_69f76e861d8c81908559031dc66e3c15 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69fcdaa2bfc08190beccabb0f1782d0d |
completed | May 7, 2026, 6:32 p.m. |
Created at: May 3, 2026, 4:31 p.m.