Triple
T28890644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Gate of Mordor |
E732683
|
entity |
| Predicate | hasAdjacentFortress |
P66389
|
FINISHED |
| Object | towers of the Teeth |
—
|
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: towers of the Teeth | Statement: [Black Gate of Mordor, hasAdjacentFortress, towers of the Teeth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdjacentFortress Context triple: [Black Gate of Mordor, hasAdjacentFortress, towers of the Teeth]
-
A.
hasFortificationNearby
chosen
Indicates that one entity is located in proximity to, or within the immediate area of, a fortification structure associated with it.
-
B.
hasFortressConstructed
Indicates that a fortress has been built or established for, by, or at the associated entity.
-
C.
containsFortress
Indicates that a location or area includes a fortress within its boundaries.
-
D.
hasNearbyMilitaryTown
Indicates that one location is situated close to a town whose primary function or identity is associated with military presence or activity.
-
E.
hasNearbyAncientCity
Indicates that one entity is located close to another entity that is classified as an ancient city.
- 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_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: April 28, 2026, 7:54 a.m.