Triple
T33217425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Gate of Mordor |
E850323
|
entity |
| Predicate | controlsPassageTo |
P15393
|
FINISHED |
| Object | Mordor |
—
|
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: Mordor | Statement: [Black Gate of Mordor, controlsPassageTo, Mordor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlsPassageTo Context triple: [Black Gate of Mordor, controlsPassageTo, Mordor]
-
A.
controlsAccessTo
chosen
Indicates that one entity regulates, manages, or determines the ability of another entity to reach, use, or interact with a resource, location, or service.
-
B.
controlsAccessBetween
Indicates that one entity regulates, manages, or restricts the ability of another entity to interact or communicate with a third entity or resource.
-
C.
entryControl
Indicates a relationship where one entity regulates or authorizes another entity’s access to a place, system, or resource.
-
D.
canControl
Indicates that one entity has the ability or authority to direct, manage, or influence the behavior or state of another entity.
-
E.
guardedPassage
Indicates that access through a passage is controlled or protected by a guard or security presence.
- 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_69f3496083dc8190b229bb6932dc548b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe68a4b67881909ca1d9f276f922e0 |
completed | May 8, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69fe680234c88190b01f953987b74972 |
completed | May 8, 2026, 10:47 p.m. |
Created at: May 1, 2026, 1:30 a.m.