Triple
T36549377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Hand of Sauron |
E901216
|
entity |
| Predicate | finalConfrontationLocation |
P81796
|
FINISHED |
| Object | Black Gate |
—
|
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: Black Gate | Statement: [Black Hand of Sauron, finalConfrontationLocation, Black Gate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalConfrontationLocation Context triple: [Black Hand of Sauron, finalConfrontationLocation, Black Gate]
-
A.
climaxLocation
chosen
Indicates the place or setting where the most intense or pivotal moment of an event, narrative, or process occurs.
-
B.
secondFightLocation
Indicates the location where the second fight or confrontation between the involved entities takes place.
-
C.
antagonistLocationFor
Indicates that a location serves as the primary place where an antagonist operates, resides, or exerts influence in relation to a given context or entity.
-
D.
victoryLocation
Indicates the place or setting where a victory or triumph occurs.
-
E.
finalHomeOf
Indicates that a location is the last or ultimate home, residence, or resting place of an 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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fed6da0390819096b88ef4714b144e |
completed | May 9, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69fed53517d081909966f31707625f1a |
completed | May 9, 2026, 6:33 a.m. |
Created at: May 3, 2026, 4:11 p.m.