Triple
T20914487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cat and Fiddle Inn |
E515034
|
entity |
| Predicate | roadIsKnownFor |
P131761
|
FINISHED |
| Object | scenic driving route |
—
|
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: scenic driving route | Statement: [Cat and Fiddle Inn, roadIsKnownFor, scenic driving route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadIsKnownFor Context triple: [Cat and Fiddle Inn, roadIsKnownFor, scenic driving route]
-
A.
isNamedRoadIn
Indicates that a specific named road is located within or belongs to a particular geographic area or region.
-
B.
roadFeature
Indicates that an entity is a specific physical or functional characteristic associated with a road, such as its structure, markings, or related infrastructure.
-
C.
roadServed
Indicates that a road is provided with necessary services or infrastructure support by a responsible entity.
-
D.
roadAssociatedWith
chosen
Indicates that there is a relevant connection or linkage between a road and another entity, such as use, location, function, or impact.
-
E.
roadTerminusOf
Indicates that a road ends at, or has its terminal point at, the referenced location or route.
- 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_69e0b4f9d5ec8190bb2bd27350ed341c |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6ec61a6ec81908d9e0629438d27c9 |
completed | April 21, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69e5c9ac91108190a6700fcdf2f11890 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:48 p.m.