Triple
T28890656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Gate of Mordor |
E732683
|
entity |
| Predicate | alternativeAccessAvoidedBy |
P124712
|
FINISHED |
| Object | Frodo and Sam via Cirith Ungol |
—
|
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: Frodo and Sam via Cirith Ungol | Statement: [Black Gate of Mordor, alternativeAccessAvoidedBy, Frodo and Sam via Cirith Ungol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alternativeAccessAvoidedBy Context triple: [Black Gate of Mordor, alternativeAccessAvoidedBy, Frodo and Sam via Cirith Ungol]
-
A.
avoidedFor
Indicates that one entity is deliberately not used, chosen, or engaged with because of the presence, influence, or characteristics of another entity.
-
B.
alternativeRoute
Indicates that there exists a different path or option that can be taken instead of the primary or original route.
-
C.
avoidsRoute
Indicates that an entity deliberately does not use or travel along a particular route.
-
D.
seeksToAvoid
Indicates an entity’s intention or effort to stay away from, prevent, or not experience another entity or situation.
-
E.
bypassedVia
chosen
Indicates that one entity is avoided, skipped, or circumvented by using another specified means, route, or method.
- 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_69f05b07bdec819080cadfe147aa1f25 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f67f7efc3c8190986d2d95b7a23729 |
completed | May 2, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 28, 2026, 7:54 a.m.