Triple
T35011977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Summurset |
E1009957
|
entity |
| Predicate | inUniverseRaceHomelandOf |
P97512
|
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: [Summurset, inUniverseRaceHomelandOf, Altmer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniverseRaceHomelandOf Context triple: [Summurset, inUniverseRaceHomelandOf, Altmer]
-
A.
inUniverseBirthplace
Indicates that an entity’s birthplace is located within a specified fictional or defined universe.
-
B.
inUniverseRaceOfReferent
chosen
Indicates that the referent belongs to, or is a member of, a particular race within a specified fictional or conceptual universe.
-
C.
homeworldType
Indicates the type or classification of a subject’s homeworld (e.g., planet, moon, habitat) in relation to that subject.
-
D.
inUniverseOrigin
Indicates that one entity originates from, or has its source within, the fictional universe or setting defined by another entity.
-
E.
inUniversePlanet
Indicates that a planet exists within or belongs to a particular fictional or defined universe.
- 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_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:01 p.m.