Triple
T16209961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sutrio |
E393435
|
entity |
| Predicate | isOneOfStartingPointsFor |
P41494
|
FINISHED |
| Object | Monte Zoncolan cycling ascent |
—
|
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: Monte Zoncolan cycling ascent | Statement: [Sutrio, isOneOfStartingPointsFor, Monte Zoncolan cycling ascent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOneOfStartingPointsFor Context triple: [Sutrio, isOneOfStartingPointsFor, Monte Zoncolan cycling ascent]
-
A.
isStartingPointOf
chosen
Indicates that something serves as the initial point or origin from which another thing, process, or path begins.
-
B.
isReferencePointFor
Indicates that one entity serves as a positional or conceptual basis used to locate, measure, or interpret another entity.
-
C.
startPointLocatedIn
Indicates that the starting point of something is geographically or spatially located within a specified area or region.
-
D.
hasStepsLeadingTo
Indicates that one location or object is connected to another by a set of steps or a staircase leading toward it.
-
E.
startPoint
Indicates the initial location or position from which an object, path, or action begins.
- 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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e22711e4fc8190bf7a9f0c59b7889f |
completed | April 17, 2026, 12:26 p.m. |
| PD | Predicate disambiguation | batch_69e219e94a448190b73a4e6aa374eb4a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.