Triple
T7405677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Quebrada |
E170862
|
entity |
| Predicate | typicalCliffHeight |
P18448
|
FINISHED |
| Object | approximately 35 meters |
—
|
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: approximately 35 meters | Statement: [La Quebrada, typicalCliffHeight, approximately 35 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCliffHeight Context triple: [La Quebrada, typicalCliffHeight, approximately 35 meters]
-
A.
hasCliffHeight
chosen
Indicates the relationship between a cliff and the measurement of its vertical height.
-
B.
hasCliffsOn
Indicates that one entity possesses or features cliffs located along or on the surface of another entity.
-
C.
hasCliffHeightCategory
Indicates the categorized height range of a cliff associated with an entity.
-
D.
rockHeight
Indicates that a rock has a specified vertical measurement or elevation (its height).
-
E.
hasCliff
Indicates that something possesses or features a steep, high rock face or abrupt vertical drop as part of its structure or environment.
- 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_69c68a6010108190925e5284de022660 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f271f1d481909a46d50b13b51a62 |
completed | March 27, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69c6f0323b2c819098ab72c33e6d8534 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:10 p.m.