Triple
T7019783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colle dell’Agnello |
E162789
|
entity |
| Predicate | hasAscentFrom |
P52151
|
FINISHED |
| Object | Italian side |
—
|
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: Italian side | Statement: [Colle dell’Agnello, hasAscentFrom, Italian side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAscentFrom Context triple: [Colle dell’Agnello, hasAscentFrom, Italian side]
-
A.
hasDescent
Indicates that one entity is a descendant of another, typically through a lineage or ancestry relationship.
-
B.
hasClimbFrom
chosen
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.
ascendedTo
Indicates that one entity rose, climbed, or moved upward to reach the position, level, or location of another entity.
-
D.
hasFirstAscensionist
Indicates that an entity (such as a route, peak, or climb) is associated with the person or group who first successfully ascended it.
-
E.
hasAltitudeFeature
Indicates that an entity possesses a characteristic or attribute related to its elevation or vertical position above a reference level.
- 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_69c6885b26248190a857541e3d10e299 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e5ecd4488190bf19e42de55da98b |
completed | March 27, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69c6e1b8118481909d76eb6616160e80 |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:34 p.m.