Triple
T35012099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altmeris |
E1009959
|
entity |
| Predicate | usedByFactionInLore |
P96829
|
FINISHED |
| Object | Altmeri Dominion |
—
|
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: Altmeri Dominion | Statement: [Altmeris, usedByFactionInLore, Altmeri Dominion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByFactionInLore Context triple: [Altmeris, usedByFactionInLore, Altmeri Dominion]
-
A.
ownerFactionLore
Indicates that a faction holds ownership or control over the subject within the context of the lore or narrative.
-
B.
associatedWithDynastyOrFaction
Indicates that an entity is linked to, belongs to, or is significantly connected with a particular dynasty or faction.
-
C.
usedByPoliticalFaction
chosen
Indicates that something (such as a resource, symbol, strategy, or tool) is employed or utilized by a specific political faction.
-
D.
foughtForFaction
Indicates that an entity actively participated in or supported a particular faction, typically in a conflict or struggle.
-
E.
historicalFaction
Indicates that an entity was a member of, associated with, or part of a particular faction or side in a historical context or conflict.
- 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_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
Created at: May 3, 2026, 4:01 p.m.