Triple
T38416644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Organ (rock formation) |
E901616
|
entity |
| Predicate | locatedNearEntranceOf |
P182625
|
FINISHED |
| Object | Arches National Park |
E46354
|
NE FINISHED |
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: Arches National Park | Statement: [The Organ (rock formation), locatedNearEntranceOf, Arches National Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedNearEntranceOf Context triple: [The Organ (rock formation), locatedNearEntranceOf, Arches National Park]
-
A.
nearestEntrance
Indicates that one entrance is the closest access point to a given location or entity compared to all other possible entrances.
-
B.
isNearEntrance
chosen
Indicates that an entity is located close to the entrance of a place or structure.
-
C.
hallLocatedNear
Indicates that a hall is situated close to another specified place or entity in physical space.
-
D.
hasEntranceOn
Indicates that one entity’s entrance or access point is located on or faces a specified side, boundary, or feature of another entity.
-
E.
isSecondaryEntranceOf
Indicates that one entrance serves as an additional or subordinate access point to a primary entrance of the same place or structure.
- F. None of above.
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_69f76e61e79c81908b787d83b46ab92b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a42e07b7ce08190a4defc5bb9fefd0b |
completed | June 29, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:31 p.m.