Triple
T37458104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Murloc |
E930848
|
entity |
| Predicate | factionRelation |
P106973
|
FINISHED |
| Object | Independent tribal communities |
—
|
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: Independent tribal communities | Statement: [Murloc, factionRelation, Independent tribal communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: factionRelation Context triple: [Murloc, factionRelation, Independent tribal communities]
-
A.
factionType
Indicates the classification or category of a faction within a broader system or context.
-
B.
factionAssociated
chosen
Indicates that an entity is connected to, aligned with, or belongs to a particular faction.
-
C.
politicalRelation
Indicates a relationship between entities that involves political alignment, influence, affiliation, conflict, or cooperation within a political context.
-
D.
vassalOrAllyOf
Indicates that one entity is subordinate to, dependent on, or formally aligned in support of another entity, typically in a hierarchical or cooperative political or military relationship.
-
E.
hasFriendshipPactWith
Indicates a mutual agreement or bond of friendship established between two entities.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.