Triple
T37705085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dazar'alor |
E939176
|
entity |
| Predicate | governingBodyInLore |
P20613
|
FINISHED |
| Object | Zandalari monarchy |
E2239138
|
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: Zandalari monarchy | Statement: [Dazar'alor, governingBodyInLore, Zandalari monarchy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingBodyInLore Context triple: [Dazar'alor, governingBodyInLore, Zandalari monarchy]
-
A.
governingBody2
Indicates that an entity serves as the official authority or administrative body responsible for overseeing, managing, or regulating another entity.
-
B.
governingBodyUsedBy
Indicates that a governing body is utilized or employed by another entity to perform governance-related functions or services.
-
C.
governingBodyOfType
Indicates that an entity serves as the official governing body for another entity of a specified type or category.
-
D.
governingBodyRepresents
Indicates that a governing body acts on behalf of, and makes decisions representing the interests or authority of, another entity.
-
E.
governingBodyExample
chosen
Indicates that the subject entity serves as an example or instance of a governing body for the object entity.
- 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_69f76edb49dc8190b951dce9ce6ef789 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0379a4086c8190a83df5570f737e15 |
completed | May 12, 2026, 7:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40d674856081909953880a1b2ec753 |
completed | June 28, 2026, 8:08 a.m. |
| PD | Predicate disambiguation | batch_6a037049db848190a6268bf1a8a60223 |
completed | May 12, 2026, 6:24 p.m. |
Created at: May 3, 2026, 4:18 p.m.