Triple
T34053578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cadair Berwyn summit ridge |
E873291
|
entity |
| Predicate | hasSummitNearby |
P200244
|
FINISHED |
| Object | Cadair Berwyn summit |
—
|
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: Cadair Berwyn summit | Statement: [Cadair Berwyn summit ridge, hasSummitNearby, Cadair Berwyn summit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSummitNearby Context triple: [Cadair Berwyn summit ridge, hasSummitNearby, Cadair Berwyn summit]
-
A.
hasSummitIn
Indicates that an entity (such as a mountain or organization) has its summit or peak located within a specified place or region.
-
B.
hasSummit
Indicates that one entity possesses, features, or includes a summit or highest point as part of its structure or characteristics.
-
C.
hasSummitTrailheadNear
Indicates that the starting point of a summit trail is located close to the referenced entity.
-
D.
hasSummitElevationApprox
Indicates that an entity has an approximate elevation value for its summit or highest point.
-
E.
hasSummitOnSideOf
Indicates that the summit or highest point of one geographic feature is located on the side of another feature.
- 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_69f349a3ec2c8190b62da76e54231a0f |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff7c96e6dc8190b89554480ebcea39 |
completed | May 9, 2026, 6:27 p.m. |
| PD | Predicate disambiguation | batch_69ff7c2381748190ad9a2176e0e478cd |
completed | May 9, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69ff7c96036c8190bfae5ec9b5a1965f |
completed | May 9, 2026, 6:27 p.m. |
Created at: May 1, 2026, 1:52 a.m.