Triple
T35525485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grande Grotta climbing sector |
E1026660
|
entity |
| Predicate | boltingStyle |
P183201
|
FINISHED |
| Object | fully bolted sport routes |
—
|
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: fully bolted sport routes | Statement: [Grande Grotta climbing sector, boltingStyle, fully bolted sport routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boltingStyle Context triple: [Grande Grotta climbing sector, boltingStyle, fully bolted sport routes]
-
A.
boltType
Indicates the specific kind or category of bolt associated with or used in relation to an entity.
-
B.
bolting
Indicates that an entity is rapidly and suddenly moving away or fleeing from another entity or location.
-
C.
boltDesign
Indicates a design relationship where one entity specifies or defines the bolt configuration, features, or parameters used in another entity.
-
D.
hasBoltHandle
Indicates that one entity is equipped with or includes a bolt-style handle associated with another entity.
-
E.
boltLockingLugs
Indicates that one entity serves as the locking lugs on a bolt that mechanically secure it in place during operation.
- F. None of above. chosen
Provenance (4 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_69f76dfe78b081908e2b14cb88dd8c00 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79a54aa3c8190b2bb5d790b2d42d4 |
completed | May 3, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69f7961970408190b669cc556e30a608 |
completed | May 3, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69f79a53ccc481908421ae16e69aa8a4 |
completed | May 3, 2026, 6:56 p.m. |
Created at: May 3, 2026, 4:04 p.m.