Triple
T32282549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sculptured Hills |
E824738
|
entity |
| Predicate | elevationRelativeToValleyFloor |
P66809
|
FINISHED |
| Object | higher |
—
|
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: higher | Statement: [Sculptured Hills, elevationRelativeToValleyFloor, higher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevationRelativeToValleyFloor Context triple: [Sculptured Hills, elevationRelativeToValleyFloor, higher]
-
A.
elevationAboveValley
chosen
Indicates the vertical height or altitude of an entity measured relative to the lowest point of the surrounding valley.
-
B.
elevationRelativeToCanyonFloor
Indicates the vertical height or altitude of something measured relative to the canyon floor as the reference level.
-
C.
valleyHeightAboveGround
Indicates the vertical distance between the valley’s lowest point and the surrounding ground level.
-
D.
elevationRelativeToCanyon
Indicates the relative height or altitude of one location compared to the canyon’s reference level.
-
E.
elevationAboveSurroundingPlains
Indicates that something is situated at a higher altitude than the nearby flat or low-lying surrounding plains.
- 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_69f3490f404081908450db66884f4334 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: May 1, 2026, 12:43 a.m.