Triple
T34095926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shiprock |
E874427
|
entity |
| Predicate | climbingBanReason |
P170043
|
FINISHED |
| Object | sacred status to Navajo |
—
|
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: sacred status to Navajo | Statement: [Shiprock, climbingBanReason, sacred status to Navajo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climbingBanReason Context triple: [Shiprock, climbingBanReason, sacred status to Navajo]
-
A.
climbingRestrictionReason
chosen
Indicates the reason why climbing is restricted or prohibited in a given context.
-
B.
climbingBanEffectiveFrom
Indicates the date or point in time from which a climbing ban starts to apply.
-
C.
hasClimbingRestriction
Indicates that there is a rule, limitation, or prohibition affecting whether and how climbing is allowed on the associated object or location.
-
D.
climbingAllowed
Indicates that an entity is permitted to climb onto or up another entity or surface.
-
E.
hasClimbingConditions
Indicates that specific environmental or situational conditions suitable for climbing are present or associated with something.
- 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_69f349a735208190a1dbfb1c2a121059 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70c5d397c8190a662b6137058c075 |
completed | May 3, 2026, 8:50 a.m. |
| PD | Predicate disambiguation | batch_69f70ac0170c819098e3b8e41d02efef |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:53 a.m.