Triple
T33759880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European long-distance hiking routes network |
E865077
|
entity |
| Predicate | routeLabelPattern |
P75208
|
FINISHED |
| Object | E1–E12 |
—
|
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: E1–E12 | Statement: [European long-distance hiking routes network, routeLabelPattern, E1–E12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeLabelPattern Context triple: [European long-distance hiking routes network, routeLabelPattern, E1–E12]
-
A.
routeSymbol
chosen
Indicates that a particular symbol or code is used to represent or identify a specific route.
-
B.
routeSegment
Indicates a specific portion of a larger route that directly connects two points or locations within that route.
-
C.
routeStyle
Indicates the manner or style in which a route is established, traveled, or executed (e.g., method, technique, or approach used for the route).
-
D.
routeExtension
Indicates that an existing route is extended beyond its original endpoint to cover additional segments or destinations.
-
E.
route
Indicates that one entity serves as a path or course used to travel or move between locations associated with 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_69f3498d3b748190aa3c4006c1f32f38 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:45 a.m.