Triple
T35220986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cave Falls |
E1016951
|
entity |
| Predicate | isNearEntrance |
P182625
|
FINISHED |
| Object | Bechler (southwest) area of Yellowstone National Park |
—
|
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: Bechler (southwest) area of Yellowstone National Park | Statement: [Cave Falls, isNearEntrance, Bechler (southwest) area of Yellowstone National Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNearEntrance Context triple: [Cave Falls, isNearEntrance, Bechler (southwest) area of Yellowstone 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.
distanceToTheEntrance
Indicates the spatial distance between a given entity and the entrance of a specified place or structure.
-
C.
hasEntranceOn
Indicates that one entity’s entrance or access point is located on or faces a specified side, boundary, or feature of another entity.
-
D.
hasNearbyGate
Indicates that one entity has a gate located in close physical proximity to it.
-
E.
hasEntrance
Indicates that one entity possesses or provides an entry point or access way to another entity or space.
- 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_69f76de072908190ab65038a8a7b6a79 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7904a770481908ef3f788e51e8dba |
completed | May 3, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
| PDg | Predicate description generation | batch_69f78f629d508190b755848162c4e101 |
completed | May 3, 2026, 6:09 p.m. |
Created at: May 3, 2026, 4:02 p.m.