Triple
T34555866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruta Nacional 68 |
E887200
|
entity |
| Predicate | popularActivityAlongRoute |
P192940
|
FINISHED |
| Object | sightseeing |
—
|
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: sightseeing | Statement: [Ruta Nacional 68, popularActivityAlongRoute, sightseeing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: popularActivityAlongRoute Context triple: [Ruta Nacional 68, popularActivityAlongRoute, sightseeing]
-
A.
popularRouteOn
Indicates that a particular route is frequently used or favored on a given transportation line, service, or network.
-
B.
popularRouteVia
Indicates that a route between two locations commonly or frequently passes through a specified intermediate point or path.
-
C.
popularRouteTo
Indicates that one location is widely used or frequently chosen as a route or way to reach another location.
-
D.
popularRouteFrom
Indicates a frequently chosen or well-traveled route that starts from a given origin location.
-
E.
travelRouteContext
Indicates the contextual details (such as purpose, conditions, or circumstances) under which a particular travel route is taken or defined.
- 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_69f349cff89081908f91e0b064f4833e |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69fd328298ac8190b6bd5ded7dca270d |
completed | May 8, 2026, 12:46 a.m. |
Created at: May 1, 2026, 2:02 a.m.