Triple
T33152879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horn of Gondor |
E848484
|
entity |
| Predicate | statusAfterBoromir |
P198498
|
FINISHED |
| Object | broken in two pieces |
—
|
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: broken in two pieces | Statement: [Horn of Gondor, statusAfterBoromir, broken in two pieces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfterBoromir Context triple: [Horn of Gondor, statusAfterBoromir, broken in two pieces]
-
A.
opponentInBattleOfTheMorannon
Indicates that two entities were opposing sides facing each other in the Battle of the Morannon.
-
B.
statusAfterBattleOfFiveArmies
Indicates the condition or state of an entity following the events of the Battle of Five Armies.
-
C.
statusAfterWarOfTheRing
Indicates the condition or role an entity has following the events of the War of the Ring.
-
D.
outcomeForGandalf
Indicates the result or consequence that specifically befalls Gandalf in a given situation or event.
-
E.
effectOfDestructionOfOneRing
Indicates the consequences or outcomes that result from the destruction of the One Ring.
- 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_69f3495a458c8190a1d34b237ba0be3f |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69feecf1bb248190ba30f0bb1d22ee08 |
completed | May 9, 2026, 8:14 a.m. |
| PD | Predicate disambiguation | batch_69feea5f27748190b223ee4e3ba5a678 |
completed | May 9, 2026, 8:03 a.m. |
| PDg | Predicate description generation | batch_69feecf102e08190b237c29e45beeca0 |
completed | May 9, 2026, 8:14 a.m. |
Created at: May 1, 2026, 1:28 a.m.