Triple
T27357314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 211 and Skyline Drive |
E685718
|
entity |
| Predicate | scenicRoadComponent |
P30397
|
FINISHED |
| Object | Skyline Drive |
—
|
NE NERFINISHED |
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: Skyline Drive | Statement: [U.S. Route 211 and Skyline Drive, scenicRoadComponent, Skyline Drive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scenicRoadComponent Context triple: [U.S. Route 211 and Skyline Drive, scenicRoadComponent, Skyline Drive]
-
A.
nearScenicRoute
Indicates that one entity is located close to a route or path that is considered scenic or visually appealing.
-
B.
roadsideFunction
Indicates that something serves a specific purpose or role related to the use, support, or operation of a roadside area.
-
C.
scenicSectionName
Indicates the specific name assigned to a scenic section or segment within a larger route, area, or context.
-
D.
roadTraverses
chosen
Indicates that a road passes through, crosses, or extends across a specified geographic area or feature.
-
E.
isScenicByway
Indicates that a roadway is officially designated as a scenic byway, recognized for its notable visual, cultural, or natural appeal along its 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_69ef14887c288190931b8431fdbf53c4 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f62c20321481908ba574ad96d93013 |
completed | May 2, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69f620e4b1c88190a17940251abc68fd |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 11:52 a.m.