Triple
T2816582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cesen Route |
E54301
|
entity |
| Predicate | popularityRelativeToOtherRoutes |
P43486
|
FINISHED |
| Object | less frequented than Abruzzi Spur |
—
|
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: less frequented than Abruzzi Spur | Statement: [Cesen Route, popularityRelativeToOtherRoutes, less frequented than Abruzzi Spur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: popularityRelativeToOtherRoutes Context triple: [Cesen Route, popularityRelativeToOtherRoutes, less frequented than Abruzzi Spur]
-
A.
isMostPopularRouteOn
Indicates that a particular route is the most frequently chosen or favored option on a given transportation line, network, or service.
-
B.
popularRouteFrom
Indicates a frequently chosen or well-traveled route that starts from a given origin location.
-
C.
difficultyRelativeToOtherRoutes
Indicates how the difficulty level of one route compares relative to other routes.
-
D.
hasTouristPopularity
Indicates that a place or attraction is recognized as being popular or frequently visited by tourists.
-
E.
hasTouristRoute
Indicates that a location or site is connected to or included in a designated tourist route or itinerary.
- 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_69ab49de0af08190b3da69683be1e728 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abdf15b7288190a03d1193cc0544a6 |
completed | March 7, 2026, 8:17 a.m. |
| PD | Predicate disambiguation | batch_69abdd08f2f481908c3da8a9c7a00552 |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abdf13d2b8819097b8edaaea90dbe2 |
completed | March 7, 2026, 8:17 a.m. |
Created at: March 6, 2026, 9:59 p.m.