Triple
T25068823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chapman's Peak |
E627852
|
entity |
| Predicate | hasScenicPullOffs |
P104364
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Chapman's Peak, hasScenicPullOffs, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScenicPullOffs Context triple: [Chapman's Peak, hasScenicPullOffs, yes]
-
A.
hasScenicPullouts
chosen
Indicates that a route or roadway includes designated scenic pullout areas where travelers can stop to view the surroundings.
-
B.
hasScenicPassNearby
Indicates that a location is situated close to a notable scenic pass, such as a mountain or landscape viewpoint route.
-
C.
hasScenicSections
Indicates that a route, path, or area contains segments that are visually attractive or offer notable scenic views.
-
D.
hasScenicDrive
Indicates that one entity offers or features a visually appealing or picturesque driving route associated with it.
-
E.
hasScenicViewpoints
Indicates that something includes or provides locations specifically intended for enjoying scenic or panoramic views.
- 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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
Created at: April 18, 2026, 6:10 a.m.