Triple
T3592438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curt Gowdy |
E76055
|
entity |
| Predicate | stateParkLocation |
P49592
|
FINISHED |
| Object | between Cheyenne and Laramie, Wyoming, United States |
—
|
LITERAL 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: between Cheyenne and Laramie, Wyoming, United States | Statement: [Curt Gowdy, stateParkLocation, between Cheyenne and Laramie, Wyoming, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateParkLocation Context triple: [Curt Gowdy, stateParkLocation, between Cheyenne and Laramie, Wyoming, United States]
-
A.
stateParkSystem
Indicates that an entity is part of, managed by, or associated with a state-level park system or network of state parks.
-
B.
countyParkOrArea
Indicates that a location is designated as a county-level park or recreational area under the jurisdiction of a county authority.
-
C.
nationalPark
Indicates that a location is designated and managed as a national park by a governing authority.
-
D.
nationalParkName
Indicates the name assigned to a national park.
-
E.
parkUnit
Indicates that one entity is a designated unit, component, or subdivision within a larger park or park system.
- 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_69ad85d8042081908af94a04c410dec0 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc15a546481909c72dac80d65e1fb |
completed | March 8, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69adb839b4e08190b1c0d611cccb11ae |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb902e61c81908f10494f828e260f |
completed | March 8, 2026, 5:59 p.m. |
Created at: March 8, 2026, 3:22 p.m.