Triple
T34797762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Argonians |
E1003134
|
entity |
| Predicate | notableFactionMembership |
P106973
|
FINISHED |
| Object | Dark Brotherhood |
E995756
|
NE 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: Dark Brotherhood | Statement: [Argonians, notableFactionMembership, Dark Brotherhood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFactionMembership Context triple: [Argonians, notableFactionMembership, Dark Brotherhood]
-
A.
notableCharacterAffiliation
Indicates that a notable character is formally associated with, aligned to, or a member of a particular group, organization, or affiliation.
-
B.
hasFaction
Indicates that an entity is affiliated with, belongs to, or is represented by a particular faction or group.
-
C.
foughtForFaction
Indicates that an entity actively participated in or supported a particular faction, typically in a conflict or struggle.
-
D.
factionAssociated
chosen
Indicates that an entity is connected to, aligned with, or belongs to a particular faction.
-
E.
factionName
Indicates the specific name assigned to a faction with which an entity is associated.
- F. None of above.
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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a376fa9e7dc8190943192fe85c15ab5 |
completed | June 21, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 3:59 p.m.