Triple
T18934826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piva River |
E463214
|
entity |
| Predicate | canyonDepthApproxM |
P79574
|
FINISHED |
| Object | up to 1200 |
—
|
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: up to 1200 | Statement: [Piva River, canyonDepthApproxM, up to 1200]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canyonDepthApproxM Context triple: [Piva River, canyonDepthApproxM, up to 1200]
-
A.
elevationRelativeToCanyonFloor
Indicates the vertical height or altitude of something measured relative to the canyon floor as the reference level.
-
B.
nearbyCanyon
Indicates that one entity is located close to a canyon in spatial proximity.
-
C.
containsCanyon
Indicates that one geographic or spatial entity includes a canyon within its boundaries or extent.
-
D.
gorgeDepth
Indicates the measured vertical distance from a gorge’s rim down to its lowest point.
-
E.
depthApprox
chosen
Indicates an approximate or estimated depth relationship between entities, rather than an exact measured depth.
- 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_69d8dcfec90481909e926be9767e5779 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d3e6a8208190973669cae439a91e |
completed | April 20, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 11:59 a.m.