Triple
T34982171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vidiian language |
E1008843
|
entity |
| Predicate | usedByFictionalRace |
P189734
|
FINISHED |
| Object | Vidiians |
—
|
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: Vidiians | Statement: [Vidiian language, usedByFictionalRace, Vidiians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByFictionalRace Context triple: [Vidiian language, usedByFictionalRace, Vidiians]
-
A.
usedByCharacterRace
Indicates that something (such as an item, ability, or feature) is utilized or employed by a particular character race.
-
B.
usedByFictionalEntity
chosen
Indicates that something (e.g., an object, tool, or resource) is utilized or employed by a fictional entity.
-
C.
fictionalSpecies
Indicates that the subject is a species that exists only in fiction or imaginary works, rather than in real life.
-
D.
raceInLegendarium
Indicates that an entity belongs to a particular fictional race or species within a specific mythological or fantasy legendarium.
-
E.
hasSpeciesInFiction
Indicates that a fictional work or universe features a particular species as part of its narrative or setting.
- 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: May 3, 2026, 4:01 p.m.