Triple
T37470362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seat of the Primus |
E931136
|
entity |
| Predicate | associatedWithFactionType |
P106973
|
FINISHED |
| Object | death-aligned covenant |
—
|
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: death-aligned covenant | Statement: [Seat of the Primus, associatedWithFactionType, death-aligned covenant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithFactionType Context triple: [Seat of the Primus, associatedWithFactionType, death-aligned covenant]
-
A.
hasFaction
Indicates that an entity is affiliated with, belongs to, or is represented by a particular faction or group.
-
B.
associatedWithDynastyOrFaction
Indicates that an entity is linked to, belongs to, or is significantly connected with a particular dynasty or faction.
-
C.
factionAssociated
chosen
Indicates that an entity is connected to, aligned with, or belongs to a particular faction.
-
D.
hasOpposingFaction
Indicates that one faction stands in opposition or conflict to another faction.
-
E.
associatedWithRebelGroup
Indicates that one entity is connected or linked in some capacity to a rebel group, such as through membership, support, collaboration, or affiliation.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.