Triple
T37440873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frank Island |
E930415
|
entity |
| Predicate | withinUSNationalPark |
P9791
|
FINISHED |
| Object | 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: Yellowstone National Park | Statement: [Frank Island, withinUSNationalPark, Yellowstone National Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: withinUSNationalPark Context triple: [Frank Island, withinUSNationalPark, Yellowstone National Park]
-
A.
withinNationalPark
chosen
Indicates that one entity is located inside the geographic boundaries of a national park designated by another entity.
-
B.
nationalParkAccess
Indicates that one entity has the right, ability, or permission to enter, use, or benefit from a specified national park.
-
C.
onlyNationalParkOf
Indicates that one entity is the sole national park associated with, or located within, a given region or jurisdiction.
-
D.
nationalPark
Indicates that a location is designated and managed as a national park by a governing authority.
-
E.
hasNationalParkServicePresence
Indicates that the National Park Service operates, manages, or maintains an official presence at the referenced location or 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_69f76ebfdcb8819098562ff3db673b04 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.