Triple
T11031965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Double Arch |
E260777
|
entity |
| Predicate | climbingRegulation |
P46978
|
FINISHED |
| Object | technical climbing generally prohibited |
—
|
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: technical climbing generally prohibited | Statement: [Double Arch, climbingRegulation, technical climbing generally prohibited]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climbingRegulation Context triple: [Double Arch, climbingRegulation, technical climbing generally prohibited]
-
A.
climbingRegulations
chosen
Indicates rules or restrictions governing how climbing activities may be conducted in a given area or context.
-
B.
climbingBanEffectiveFrom
Indicates the date or point in time from which a climbing ban starts to apply.
-
C.
climbingArea
Indicates that one entity is a designated location or site used for climbing activities in relation to another entity.
-
D.
climbingPermitRequired
Indicates that performing a climbing activity at a given location or on a given route is contingent upon obtaining a formal permit or authorization.
-
E.
climbingActivity
Indicates an activity where an entity ascends or scales a surface, structure, or natural formation, typically using physical effort and coordination.
- 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_69d6aa979bdc8190bf0e79104cc098c1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797e58aec8190bb8ffdc71c0614d2 |
completed | April 9, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69d7440087ac8190aef2e6f6b13b2635 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:25 p.m.