Triple
T35471395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exo |
E1025216
|
entity |
| Predicate | playableRaceIn |
P98927
|
FINISHED |
| Object | Destiny |
—
|
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: Destiny | Statement: [Exo, playableRaceIn, Destiny]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playableRaceIn Context triple: [Exo, playableRaceIn, Destiny]
-
A.
playableRace
chosen
Indicates that an entity is a race or species that players are allowed to choose and control in a game or interactive system.
-
B.
relatedRace
Indicates that there is a connection or association between two races, such as similarity, relevance, or contextual linkage.
-
C.
appearsInRace
Indicates that an entity participates as a competitor or entrant in a specific race event.
-
D.
hasPlayableCharacter
Indicates that an entity includes or is associated with a character that a user can control or play as.
-
E.
usedByCharacterRace
Indicates that something (such as an item, ability, or feature) is utilized or employed by a particular character race.
- 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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.