Triple
T27680893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beartooth Highway |
E697903
|
entity |
| Predicate | accessesRegionOf |
P78464
|
FINISHED |
| Object | northeastern 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: northeastern Yellowstone National Park | Statement: [Beartooth Highway, accessesRegionOf, northeastern Yellowstone National Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessesRegionOf Context triple: [Beartooth Highway, accessesRegionOf, northeastern Yellowstone National Park]
-
A.
accessesRegion
chosen
Indicates that one entity reaches, uses, or interacts with a specific geographic or logical region.
-
B.
isRegionOf
Indicates that one entity is a geographic or administrative region belonging to, contained within, or associated with another entity.
-
C.
occupiedRegion
Indicates that an entity has taken control of and is currently holding a specific geographic area or region.
-
D.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
E.
guardedRegion
Indicates that a region is protected or watched over by some guarding entity or mechanism.
- 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_69ef590d458c81909583290c3cd0478b |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 27, 2026, 2:46 p.m.