Triple
T22646102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colonel By Drive |
E558965
|
entity |
| Predicate | partOfScenicSystem |
P41742
|
FINISHED |
| Object | NCC scenic drives in Ottawa |
—
|
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: NCC scenic drives in Ottawa | Statement: [Colonel By Drive, partOfScenicSystem, NCC scenic drives in Ottawa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfScenicSystem Context triple: [Colonel By Drive, partOfScenicSystem, NCC scenic drives in Ottawa]
-
A.
isPartOfScenicVista
chosen
Indicates that something is included within, or contributes to, a larger scenic vista or panoramic view.
-
B.
isScenicArea
Indicates that a location is recognized as a scenic area, typically valued for its natural beauty or visually appealing surroundings.
-
C.
hasScenicAccessTo
Indicates that one place or object provides a visually appealing or notable view of another place or object.
-
D.
hasScenicPassNearby
Indicates that a location is situated close to a notable scenic pass, such as a mountain or landscape viewpoint route.
-
E.
partOfScene
Indicates that one entity functions as a component or element within a larger scene or setting involving another entity.
- 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_69e24547f7fc819086e2c4ba3b979657 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f170371fe08190a6a53809d185f8b5 |
completed | April 29, 2026, 2:43 a.m. |
| PD | Predicate disambiguation | batch_69ee6294c4c08190b7e4829f4b9af24b |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:05 p.m.