Triple
T11049401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Doom |
E261206
|
entity |
| Predicate | climacticEventLocation |
P81796
|
FINISHED |
| Object | destruction of the One Ring |
—
|
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: destruction of the One Ring | Statement: [Mount Doom, climacticEventLocation, destruction of the One Ring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climacticEventLocation Context triple: [Mount Doom, climacticEventLocation, destruction of the One Ring]
-
A.
climaxLocation
chosen
Indicates the place or setting where the most intense or pivotal moment of an event, narrative, or process occurs.
-
B.
eventLocationOfNotableActivity
Indicates that a location is the place where a notable or significant activity or event involving the related entity occurred.
-
C.
locationOfEventDescribed
Indicates that one entity is the place or setting where the event described by another entity occurs.
-
D.
cultLocation
Indicates that a cult or religious group is based in, practices in, or is primarily associated with a particular location.
-
E.
locationOfCompetition
Indicates the place or venue where a competition or contest takes or took place.
- 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79867fa28819094f564273e3ef51d |
completed | April 9, 2026, 12:15 p.m. |
| PD | Predicate disambiguation | batch_69d7440da46c8190a77380d5d747ac9c |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.