Triple
T15395261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Col d’Èze |
E368160
|
entity |
| Predicate | hasClimbUse |
P66883
|
FINISHED |
| Object | race training climb |
—
|
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: race training climb | Statement: [Col d’Èze, hasClimbUse, race training climb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClimbUse Context triple: [Col d’Èze, hasClimbUse, race training climb]
-
A.
canClimb
Indicates that one entity has the ability or permission to climb another entity or surface.
-
B.
hasClimbFrom
Indicates a relationship where one location or object serves as the starting point from which a climb or ascent to another location or object begins.
-
C.
climbingUse
chosen
Indicates that an entity uses or employs another entity as equipment, support, or aid specifically for climbing activities.
-
D.
hasClimbSide
Indicates that one entity has a particular side or surface that is suitable or designated for climbing.
-
E.
canBeClimbedIn
Indicates that one entity is suitable or possible to climb while being inside or within 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_69d85a16c68c819099c1b547fbc87b32 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e8ac79081908ac79c0b3e7587ff |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27b8cac8190bfa77698d53c5d1c |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:19 a.m.