Triple
T35012228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Auridon |
E1009962
|
entity |
| Predicate | hasPrimaryAlliance |
P133749
|
FINISHED |
| Object | Aldmeri Dominion |
E1009954
|
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: Aldmeri Dominion | Statement: [Auridon, hasPrimaryAlliance, Aldmeri Dominion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryAlliance Context triple: [Auridon, hasPrimaryAlliance, Aldmeri Dominion]
-
A.
hasOpposingAlliance
Indicates that two entities belong to alliances or factions that are in direct opposition or conflict with each other.
-
B.
operatesInAlliance
Indicates that one entity conducts its activities in cooperation or coordination with another entity as part of a formal or informal alliance.
-
C.
involvesAlliance
chosen
Indicates that there exists a cooperative or strategic alliance relationship between the referenced entities.
-
D.
recognizedAlliance
Indicates that one party formally acknowledges the existence and validity of an alliance involving another party.
-
E.
appliedInAlliance
Indicates that something (such as a method, strategy, or resource) is used or implemented within the context of an alliance or partnership between parties.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a034ca1a8d88190bd44f33814436e59 |
completed | May 12, 2026, 3:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a385bb76acc819094bf1376c490a45f |
completed | June 21, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_6a034b591f2481908e05562841c9a3c2 |
completed | May 12, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.