Triple
T36843967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kin-strife in Gondor |
E910487
|
entity |
| Predicate | locationOfMajorBattle |
P12233
|
FINISHED |
| Object | Osgiliath |
E271243
|
NE 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: Osgiliath | Statement: [Kin-strife in Gondor, locationOfMajorBattle, Osgiliath]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfMajorBattle Context triple: [Kin-strife in Gondor, locationOfMajorBattle, Osgiliath]
-
A.
battleSignificanceAtLocation
Indicates the degree of importance or impact that a particular battle has at a specified location.
-
B.
locationOfMajorDefeat
Indicates the place where a significant or decisive defeat of a party occurred.
-
C.
battleOccurredOn
chosen
Indicates that a specific battle took place at or on a particular location or date.
-
D.
battleOccurredNear
Indicates that a battle took place in spatial proximity to a specified location or entity.
-
E.
hasSignificantBattle
Indicates that a major or decisive battle occurred involving the related entities.
- F. None of above.
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_69f76e7f65a881908651b702da592b6d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40951606b48190ab48dbd8ecb29e2b |
completed | June 28, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:13 p.m.