Triple
T30633267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arnor |
E779765
|
entity |
| Predicate | destroyedInBattle |
P31453
|
FINISHED |
| Object | Battle of Fornost |
—
|
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: Battle of Fornost | Statement: [Arnor, destroyedInBattle, Battle of Fornost]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: destroyedInBattle Context triple: [Arnor, destroyedInBattle, Battle of Fornost]
-
A.
sufferedDestructionIn
chosen
Indicates that an entity experienced damage, ruin, or devastation during or as part of a specified event or period.
-
B.
killedOrCaptured
Indicates that one entity has either killed or taken another entity into custody or control.
-
C.
sufferedDestructionOf
Indicates that one entity experienced damage, ruin, or loss as a result of the destruction of another entity.
-
D.
killedInAttack
Indicates that an entity died as a direct result of a specific attack event.
-
E.
diedInConflictWith
Indicates that an entity lost their life as a direct result of a specific conflict involving another entity.
- 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_69f224a431548190a44ad9d088dbf91f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a1ee6348190a316b92bccd14826 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:28 p.m.