Triple
T38448937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West-gate of Moria |
E906713
|
entity |
| Predicate | openedOnto |
P4864
|
FINISHED |
| Object | Hollin |
—
|
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: Hollin | Statement: [West-gate of Moria, openedOnto, Hollin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedOnto Context triple: [West-gate of Moria, openedOnto, Hollin]
-
A.
openedIn
Indicates that an entity (such as a business, event, or institution) began operating or was inaugurated in a specific time period or location.
-
B.
opensOn
Indicates that an entity begins operating, becomes accessible, or starts being available at a specified time or on a specified date.
-
C.
openedAlong
Indicates that one entity was opened or inaugurated at the same time or in parallel with another entity.
-
D.
opens
chosen
Indicates that one entity causes or allows another entity (such as an object, space, or resource) to become accessible or no longer closed.
-
E.
openedAs
Indicates that one entity began operating, functioning, or being available to the public under the form, name, or role of another 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_69f76e72878c8190a692836c8b01b58b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fde5d7d9548190880a9d95b8f0f66b |
completed | May 8, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69fde4e1bf9c81909754545275eccc03 |
completed | May 8, 2026, 1:28 p.m. |
Created at: May 3, 2026, 4:31 p.m.