Triple
T33217426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Gate of Mordor |
E850323
|
entity |
| Predicate | controlsPassageThrough |
P196834
|
FINISHED |
| Object | Cirith Gorgor |
—
|
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: Cirith Gorgor | Statement: [Black Gate of Mordor, controlsPassageThrough, Cirith Gorgor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlsPassageThrough Context triple: [Black Gate of Mordor, controlsPassageThrough, Cirith Gorgor]
-
A.
isPassedThroughBy
Indicates that something serves as a medium, route, or channel through which another thing moves, flows, or is transmitted.
-
B.
passesThroughMatter
Indicates that something moves through or penetrates a material substance without being completely blocked or stopped by it.
-
C.
passesThroughArea
Indicates that an entity moves or extends through the spatial region defined by another entity or area.
-
D.
supportsPassthrough
Indicates that one entity enables or allows another entity’s data, signals, or operations to pass through it unchanged.
-
E.
passesUnder
Indicates that one entity moves or extends beneath another entity, typically crossing below it without direct contact.
- F. None of above. chosen
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_69f3496083dc8190b229bb6932dc548b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe6b7c785c8190aaab06019f571434 |
completed | May 8, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fe68edef20819081c77f9607b944dd |
completed | May 8, 2026, 10:51 p.m. |
| PDg | Predicate description generation | batch_69fe6b7a823881909dc2037fe25bea24 |
completed | May 8, 2026, 11:02 p.m. |
Created at: May 1, 2026, 1:30 a.m.