Triple
T32097020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Durin's Bane |
E819745
|
entity |
| Predicate | dwellsUnder |
P42731
|
FINISHED |
| Object | the Misty Mountains |
—
|
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: the Misty Mountains | Statement: [Durin's Bane, dwellsUnder, the Misty Mountains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dwellsUnder Context triple: [Durin's Bane, dwellsUnder, the Misty Mountains]
-
A.
burrowsIn
Indicates that one entity digs into and creates or occupies a tunnel or hole within another entity or medium.
-
B.
hasSubterraneanCreatures
Indicates that an entity contains, harbors, or is associated with creatures living beneath the ground or surface.
-
C.
breedsIn
Indicates that an organism reproduces or carries out its breeding activities within a specified environment, habitat, or location.
-
D.
subterranean
chosen
Indicates that one entity is located beneath the surface of the ground or under another structure or area.
-
E.
otherInhabitants
Indicates that there exist additional beings or residents associated with or present in the same place, group, or context as a referenced entity.
- 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_69f34901106881908ea893ad504a08be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b967d5308190bbb66d0a8dd52612 |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:26 a.m.