Triple
T33975854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morannon |
E871136
|
entity |
| Predicate | controlsPass |
P15393
|
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: [Morannon, controlsPass, Cirith Gorgor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlsPass Context triple: [Morannon, controlsPass, Cirith Gorgor]
-
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.
controlsWith
Indicates that one entity exercises authority, direction, or regulatory power over another entity through specific means or mechanisms.
-
C.
canPass
Indicates that one entity is able or permitted to move through, cross, or successfully traverse another entity or barrier.
-
D.
canControl
Indicates that one entity has the ability or authority to direct, manage, or influence the behavior or state of another entity.
-
E.
controlStatus
Indicates that one entity has a particular level, state, or condition of control over another entity or process.
- 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_69f3499da0188190ab1a4ff06fb06a2a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe8f74748c8190bd14a856c057f9f7 |
completed | May 9, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_69fe8e7ed8088190929e0df67aca4de9 |
completed | May 9, 2026, 1:31 a.m. |
Created at: May 1, 2026, 1:50 a.m.