Triple
T32170902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hornburg |
E821706
|
entity |
| Predicate | partOfFortress |
P189559
|
FINISHED |
| Object | Helm's Deep |
—
|
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: Helm's Deep | Statement: [Hornburg, partOfFortress, Helm's Deep]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfFortress Context triple: [Hornburg, partOfFortress, Helm's Deep]
-
A.
partOfMilitaryStructure
Indicates that one entity is a component, unit, or subdivision within the organizational hierarchy of a military structure.
-
B.
withinFortifications
chosen
Indicates that one entity is located inside the defensive structures or fortifications of another entity.
-
C.
locatedInFortress
Indicates that an entity is situated within the boundaries or interior of a fortress.
-
D.
fortifiedBuilding
Indicates that a building is strengthened or reinforced for defense against attacks or intrusions.
-
E.
containsFortress
Indicates that a location or area includes a fortress within its boundaries.
- 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_69f3490699a48190bbef96b198e8fade |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff8ba3f8248190bbdf8e7ec2b35093 |
completed | May 9, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69ff8b41ba988190a7332e8317d10f09 |
completed | May 9, 2026, 7:30 p.m. |
Created at: May 1, 2026, 12:33 a.m.