Triple
T37509742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Angrathar the Wrathgate |
E932185
|
entity |
| Predicate | commanderForAlliance |
P42419
|
FINISHED |
| Object | Bolvar Fordragon |
—
|
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: Bolvar Fordragon | Statement: [Battle of Angrathar the Wrathgate, commanderForAlliance, Bolvar Fordragon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commanderForAlliance Context triple: [Battle of Angrathar the Wrathgate, commanderForAlliance, Bolvar Fordragon]
-
A.
commanderForAllies
chosen
Indicates that an entity serves as a military leader or commanding authority on behalf of allied forces.
-
B.
overallAlliedCommander
Indicates that one entity serves as the highest-ranking commander with ultimate authority over all allied forces associated with the other entity.
-
C.
commander
Indicates that one entity holds authoritative military or organizational control over another entity or group.
-
D.
UnionCommanderOfAssault
Indicates that the subject served as the commanding Union officer in charge of a specific military assault.
-
E.
commandersSide
Indicates that one entity is on the same side, faction, or team as the commander in a conflict or competitive context.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdd2be648c8190b60b3d1caeb44364 |
completed | May 8, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69fdd14a5c708190a6f95ec61f4fc28f |
completed | May 8, 2026, 12:04 p.m. |
Created at: May 3, 2026, 4:17 p.m.