Triple
T2136691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chew Reservoir |
E46669
|
entity |
| Predicate | hasSurroundingFeature |
P13155
|
FINISHED |
| Object | gritstone edges |
—
|
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: gritstone edges | Statement: [Chew Reservoir, hasSurroundingFeature, gritstone edges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurroundingFeature Context triple: [Chew Reservoir, hasSurroundingFeature, gritstone edges]
-
A.
hasSurroundings
chosen
Indicates that an entity is located within or encircled by a particular environment, context, or set of surrounding elements.
-
B.
hasBoundaryFeature
Indicates that a boundary (such as an edge, border, or limit) of one entity is characterized, marked, or defined by a specific feature or element.
-
C.
hasNearbyMode
Indicates that one entity has another entity located close enough to be considered in its immediate vicinity or surrounding area.
-
D.
hasStructureOnOrAdjacent
Indicates that one entity has a physical structure located on it or immediately next to it.
-
E.
withinFeature
Indicates that one entity is spatially contained inside or lies entirely within the bounds of another feature.
- 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_69a88a174ab48190a5db20c132e5dccf |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abbf74147c81908793c3694894f94a |
completed | March 7, 2026, 6:02 a.m. |
| PD | Predicate disambiguation | batch_69abbd96a3b0819081efbfef975e1513 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:44 p.m.