Triple
T36556201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eärnur |
E901704
|
entity |
| Predicate | roleInBattleOfFornost |
P203524
|
FINISHED |
| Object | captain of Gondor’s forces |
—
|
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: captain of Gondor’s forces | Statement: [Eärnur, roleInBattleOfFornost, captain of Gondor’s forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInBattleOfFornost Context triple: [Eärnur, roleInBattleOfFornost, captain of Gondor’s forces]
-
A.
roleInBattleOfFiveArmies
Indicates the specific function, position, or involvement an entity had in the Battle of Five Armies.
-
B.
roleInWarOfTheRing
Indicates the specific function, position, or involvement an entity had within the events of the War of the Ring.
-
C.
opponentInBattleOfTheMorannon
Indicates that two entities were opposing sides facing each other in the Battle of the Morannon.
-
D.
sideInWarOfTheRing
Indicates the faction or alignment a participant belongs to in the context of the War of the Ring conflict.
-
E.
roleInHeorot
Indicates a person's specific function, position, or responsibility within the social or organizational setting of Heorot.
- 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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a019b8995dc819088727aa023beadce |
completed | May 11, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_6a01961bb748819096a941f1b5443908 |
completed | May 11, 2026, 8:40 a.m. |
| PDg | Predicate description generation | batch_6a019b88bbc88190924c1f0cdea6dd79 |
completed | May 11, 2026, 9:04 a.m. |
Created at: May 3, 2026, 4:11 p.m.