Triple
T1052095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Utah |
E22720
|
entity |
| Predicate | hasAbundantLandform |
P940
|
FINISHED |
| Object | red rock formations |
—
|
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: red rock formations | Statement: [Utah, hasAbundantLandform, red rock formations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAbundantLandform Context triple: [Utah, hasAbundantLandform, red rock formations]
-
A.
hasLandform
chosen
Indicates that one entity possesses, contains, or is characterized by a particular natural landform.
-
B.
hasNaturalFeature
Indicates that one entity possesses, contains, or is characterized by a particular natural feature (such as a mountain, river, forest, or coastline).
-
C.
hasLandscapeFeatures
Indicates that an entity possesses or includes specific landscape-related characteristics or elements.
-
D.
hasMajorMountainRange
Indicates that one entity possesses, contains, or is geographically associated with a principal or significant mountain range.
-
E.
hasLargestContinuousLandAreaOn
Indicates that an entity possesses the greatest uninterrupted expanse of land on a specified geographic region or surface compared to all other entities.
- 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_69a493da02e081908c13ff5e02a0fe7a |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b8b5312081909796df58fa7c1e9d |
completed | March 1, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69a4b7309cc481908ed839b0b8d75dbf |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.