Triple
T14461480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rancor |
E358592
|
entity |
| Predicate | speciesNameInUniverse |
P114740
|
FINISHED |
| Object | rancor |
—
|
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: rancor | Statement: [Rancor, speciesNameInUniverse, rancor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: speciesNameInUniverse Context triple: [Rancor, speciesNameInUniverse, rancor]
-
A.
speciesInUniverse
Indicates that a given species exists within, or is a member of, a particular fictional or defined universe.
-
B.
alienSpeciesName
Indicates that an entity is identified by the proper name of an alien species.
-
C.
typeSpecies
Indicates that a species is the designated type species that defines and anchors the taxonomic concept of a higher-level group (such as a genus).
-
D.
inUniverseOwnerSpecies
Indicates that a particular species is recognized as the canonical or in-universe owner of something within a fictional or defined universe.
-
E.
creatorSpecies
Indicates that one entity is the species or kind of being that created or originated another entity.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91abc1008190a19de4f8f0112c9d |
completed | April 14, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69de5c42bd3c81909a62acf30cc24d1e |
completed | April 14, 2026, 3:24 p.m. |
| PDg | Predicate description generation | batch_69de610330a48190b558235a14c0dc9f |
completed | April 14, 2026, 3:45 p.m. |
Created at: April 10, 2026, 1:19 a.m.