Triple
T35765412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thurat Range |
E1034002
|
entity |
| Predicate | hasClimbingCharacteristic |
P184054
|
FINISHED |
| Object | steep rock faces |
—
|
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: steep rock faces | Statement: [Thurat Range, hasClimbingCharacteristic, steep rock faces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClimbingCharacteristic Context triple: [Thurat Range, hasClimbingCharacteristic, steep rock faces]
-
A.
climbCharacteristic
Indicates a characteristic or property related to how an entity climbs or performs climbing actions.
-
B.
climbingFeatures
chosen
Indicates that one entity possesses or includes specific features or characteristics that facilitate or are used for climbing.
-
C.
hasClimbingActivity
Indicates that an entity engages in or is associated with a climbing-related activity.
-
D.
hasClimb
Indicates that an entity performs or is capable of performing a climbing action on or over another entity or surface.
-
E.
hasClimbingElement
Indicates that one entity includes or features a component intended for climbing by another entity.
- 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_69f76e13edd081909101629aa829c4ad |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd9ff026a48190bfec33deeb3b2c43 |
completed | May 8, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69fd97d805bc8190ba12f429d3ad04c7 |
completed | May 8, 2026, 7:59 a.m. |
Created at: May 3, 2026, 4:06 p.m.