Triple
T11637495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hermitage |
E276562
|
entity |
| Predicate | hasNearbyWalkingRoute |
P76707
|
FINISHED |
| Object | local countryside paths |
—
|
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: local countryside paths | Statement: [Hermitage, hasNearbyWalkingRoute, local countryside paths]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyWalkingRoute Context triple: [Hermitage, hasNearbyWalkingRoute, local countryside paths]
-
A.
hasNearbyWalkingRoutes
chosen
Indicates that there are walkable paths or routes located close to the referenced entity.
-
B.
hasWalkingRouteType
Indicates that an entity is associated with a specific type or category of walking route (e.g., trail, path, or walking itinerary).
-
C.
hasWalkingRouteConnection
Indicates that there is a walkable path or route directly connecting two locations.
-
D.
hasWalkingPathAround
Indicates that one entity has a walking path that encircles or runs around another entity.
-
E.
hasNearbyCycleRoute
Indicates that an entity is located close to a designated cycling route or path.
- 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_69d6aafa51148190ab84940694c00235 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a25d80208190b33e95db2e7cc276 |
completed | April 10, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69d85dd94bdc819091fa2ed33eb31624 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.