Triple
T38494386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dagorlad |
E919647
|
entity |
| Predicate | battleCommanderOpposing |
P87947
|
FINISHED |
| Object | Sauron |
—
|
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: Sauron | Statement: [Dagorlad, battleCommanderOpposing, Sauron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battleCommanderOpposing Context triple: [Dagorlad, battleCommanderOpposing, Sauron]
-
A.
opposingCommander
Indicates that one entity serves as the commanding officer of a force that is in opposition or conflict with the force commanded by another entity.
-
B.
opposingCommanderSide
chosen
Indicates that one commander is on the opposing or enemy side relative to another commander in a conflict or confrontation.
-
C.
opponentCommanderAttacker
Indicates that the referenced commander is the opposing side’s commander who is initiating or carrying out an attack.
-
D.
commandedForcesAgainst
Indicates that one entity held command authority over military or armed forces engaged in opposition to another entity.
-
E.
commanderBelligerent2
Indicates that the subject serves as a commander for the second belligerent party in a conflict or war.
- 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_69f76e9ddd4481908f8c04439d848f9d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: May 3, 2026, 4:31 p.m.