Triple
T28890690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Towers of the Teeth |
E732684
|
entity |
| Predicate | guardedStructure |
P166513
|
FINISHED |
| Object | Morannon |
—
|
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: Morannon | Statement: [Towers of the Teeth, guardedStructure, Morannon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guardedStructure Context triple: [Towers of the Teeth, guardedStructure, Morannon]
-
A.
hasProtectedStructure
Indicates that an entity possesses or is associated with a structure that is designated as protected (e.g., legally, environmentally, or culturally safeguarded).
-
B.
guardedAs
Indicates that one entity is protected, watched over, or kept secure in the role or capacity specified by another entity.
-
C.
guardedSectionOf
Indicates a relationship where one entity serves as a protective or security boundary for a specific section or portion of another entity.
-
D.
guardedRegion
Indicates that a region is protected or watched over by some guarding entity or mechanism.
-
E.
guardedSecretBy
Indicates that a secret is being protected or kept confidential by a specific entity.
- 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_69f05b07bdec819080cadfe147aa1f25 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6622808b48190bbabcc75288ab031 |
completed | May 2, 2026, 8:44 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f6617a7e7c81908cfac4a2250797ee |
completed | May 2, 2026, 8:41 p.m. |
Created at: April 28, 2026, 7:55 a.m.