Triple
T25068812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chapman's Peak |
E627852
|
entity |
| Predicate | hasCliffsideTunnels |
P160094
|
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, hasCliffsideTunnels, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCliffsideTunnels Context triple: [Chapman's Peak, hasCliffsideTunnels, yes]
-
A.
hasCliffRoad
Indicates that one location or area is connected to or characterized by a road that runs along or near a cliff.
-
B.
hasCliffs
Indicates that something possesses or is characterized by the presence of cliffs.
-
C.
hasRockTunnel
Indicates that one entity possesses, contains, or provides access to a tunnel that passes through rock.
-
D.
hasCliff
Indicates that something possesses or features a steep, high rock face or abrupt vertical drop as part of its structure or environment.
-
E.
hasCliffsOn
Indicates that one entity possesses or features cliffs located along or on the surface of another entity.
- F. None of above. chosen
Provenance (4 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_69f6018f91248190985323d1a678e539 |
completed | May 2, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f5ffc6268c8190b63f6360ebadab73 |
completed | May 2, 2026, 1:44 p.m. |
Created at: April 18, 2026, 6:10 a.m.