Triple
T38588526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle for Lordaeron |
E932399
|
entity |
| Predicate | leaderOnHordeSide |
P65676
|
FINISHED |
| Object | Sylvanas Windrunner |
—
|
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: Sylvanas Windrunner | Statement: [Battle for Lordaeron, leaderOnHordeSide, Sylvanas Windrunner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leaderOnHordeSide Context triple: [Battle for Lordaeron, leaderOnHordeSide, Sylvanas Windrunner]
-
A.
hasEnemyLeader
Indicates that one entity is the primary opposing or adversarial leader in relation to another entity.
-
B.
leaderAtFormation
Indicates that an entity served as the leader of a group or organization at the time the group or organization was first formed.
-
C.
commanderOfVictoriousSide
Indicates that one entity served as the commanding leader of the side that achieved victory in a conflict or competition relative to another entity.
-
D.
leaderOfGroup
chosen
Indicates that an entity holds a leadership role or primary authority over a particular group.
-
E.
leaderSince
Indicates that an entity has held a leadership role over another entity starting from a specified point in time.
- 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_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: May 3, 2026, 4:32 p.m.