Triple
T38588523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle for Lordaeron |
E932399
|
entity |
| Predicate | leaderOnAllianceSide |
P118322
|
FINISHED |
| Object | Anduin Wrynn |
—
|
NE NERFINISHED |
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: Anduin Wrynn | Statement: [Battle for Lordaeron, leaderOnAllianceSide, Anduin Wrynn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leaderOnAllianceSide Context triple: [Battle for Lordaeron, leaderOnAllianceSide, Anduin Wrynn]
-
A.
hasAlliedLeader
chosen
Indicates that one entity serves as an allied leader or commander in relation to another entity.
-
B.
relativeByAlliance
Indicates a familial or kinship relationship that exists due to an alliance, such as marriage or a formal pact, rather than by blood.
-
C.
leaderParty
Indicates that a given political party is the one to which a specified leader belongs or is affiliated.
-
D.
allianceRole
Indicates the specific function, status, or responsibility an entity holds within an alliance or cooperative partnership.
-
E.
leaderPosition
Indicates that one entity holds a leadership role or position of authority over another entity or within a specified group or organization.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
Created at: May 3, 2026, 4:32 p.m.