Triple
T38583706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blood Elf |
E932299
|
entity |
| Predicate | formerFactionAlignment |
P203330
|
FINISHED |
| Object | Alliance |
—
|
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: Alliance | Statement: [Blood Elf, formerFactionAlignment, Alliance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerFactionAlignment Context triple: [Blood Elf, formerFactionAlignment, Alliance]
-
A.
formerAllyOf
Indicates that an entity was once an ally of another entity but that alliance has since ended.
-
B.
predecessorFaction
Indicates that one faction historically preceded and was replaced or succeeded by another faction.
-
C.
opponentForceAllegiance
Indicates that one force, group, or individual is aligned with or belongs to an opposing or enemy side in a conflict or competition.
-
D.
formerEnemyOf
Indicates that one entity was previously an enemy of another entity, but that adversarial relationship no longer holds.
-
E.
formerClan
Indicates that an entity previously belonged to a particular clan but is no longer a member of it.
- F. None of above. chosen
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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a015ff02814819094806517fc4c69fa |
completed | May 11, 2026, 4:49 a.m. |
| PD | Predicate disambiguation | batch_6a0154ddd3c48190b85f9f48731cfd8f |
completed | May 11, 2026, 4:02 a.m. |
| PDg | Predicate description generation | batch_6a015fef7ae8819096c159ff0b259e1f |
completed | May 11, 2026, 4:49 a.m. |
Created at: May 3, 2026, 4:32 p.m.