Triple
T33152881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horn of Gondor |
E848484
|
entity |
| Predicate | locationAfterBreaking |
P30968
|
FINISHED |
| Object | Minas Tirith |
E199107
|
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: Minas Tirith | Statement: [Horn of Gondor, locationAfterBreaking, Minas Tirith]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationAfterBreaking Context triple: [Horn of Gondor, locationAfterBreaking, Minas Tirith]
-
A.
locatedAfter
Indicates that one entity is positioned later than another along a defined sequence, order, or spatial/temporal axis.
-
B.
locationAfterConversion
Indicates the place or position an entity occupies after it has been transformed, converted, or changed from one state or form to another.
-
C.
laterLocation
Indicates that an entity is located at a specified place at a later time than some reference time or earlier location.
-
D.
reentryBreakupLocation
chosen
Indicates the location where an object breaks up or disintegrates during its reentry into an atmosphere.
-
E.
landingAfterAction
Indicates that one entity performs a landing event that occurs after a specified preceding action has taken place.
- 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_69f3495a458c8190a1d34b237ba0be3f |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0361c6d76481909332b28ab01b0ef7 |
completed | May 12, 2026, 5:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a363c71eb3c819082fbcb7f565aa891 |
completed | June 20, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_6a0360b3818c819084bbecf705475f4f |
completed | May 12, 2026, 5:17 p.m. |
Created at: May 1, 2026, 1:28 a.m.