Triple
T35059493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dead Horse Ranch |
E1011554
|
entity |
| Predicate | landInspired |
P182060
|
FINISHED |
| Object | Dead Horse Ranch State Park |
E309853
|
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: Dead Horse Ranch State Park | Statement: [Dead Horse Ranch, landInspired, Dead Horse Ranch State Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landInspired Context triple: [Dead Horse Ranch, landInspired, Dead Horse Ranch State Park]
-
A.
land
Indicates coming down from the air or a higher position to make contact with and settle on a surface.
-
B.
landVariant
Indicates that one landform, terrain type, or land-related entity is an alternative or variant form of another.
-
C.
Land
Indicates that an entity arrives onto and comes to rest on a surface or ground, typically from the air or another elevated position.
-
D.
landComponent
Indicates that one entity is a physical land portion or segment that forms part of a larger land area or land-related whole.
-
E.
landscapeValue
Indicates the assessed aesthetic, cultural, or ecological worth attributed to a particular landscape or scenery.
- F. None of above. chosen
Provenance (5 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_69f76dd09c308190a523454853ce842b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7865578d48190bf90e470634fd97d |
completed | May 3, 2026, 5:31 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37d942367c8190a626850f6ac58d63 |
completed | June 21, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f78575917481909a3defd6a4c366bd |
completed | May 3, 2026, 5:27 p.m. |
Created at: May 3, 2026, 4:01 p.m.