Triple
T35011826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aldmeri Dominion |
E1009954
|
entity |
| Predicate | leaderRace |
P178848
|
FINISHED |
| Object | Altmer |
—
|
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: Altmer | Statement: [Aldmeri Dominion, leaderRace, Altmer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leaderRace Context triple: [Aldmeri Dominion, leaderRace, Altmer]
-
A.
playableRace
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.
raceInLegendarium
Indicates that an entity belongs to a particular fictional race or species within a specific mythological or fantasy legendarium.
-
D.
bearerRace
chosen
Indicates the racial or ethnic classification associated with the bearer in the relationship.
-
E.
sisterRace
Indicates that two races or species are closely related or derived from a common origin, often treated as parallel or counterpart groups.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:01 p.m.