Triple
T10743574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skywalk lookout |
E253388
|
entity |
| Predicate | elevationRelativeToForest |
P38218
|
FINISHED |
| Object | above rainforest canopy |
—
|
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: above rainforest canopy | Statement: [Skywalk lookout, elevationRelativeToForest, above rainforest canopy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevationRelativeToForest Context triple: [Skywalk lookout, elevationRelativeToForest, above rainforest canopy]
-
A.
elevationFrom
chosen
Indicates a vertical distance relationship where one entity’s height or altitude is measured relative to another reference entity.
-
B.
elevationBy
Indicates a relationship where one entity raises, increases, or enhances the level, status, or intensity of another entity.
-
C.
elevationAboveValley
Indicates the vertical height or altitude of an entity measured relative to the lowest point of the surrounding valley.
-
D.
foundInElevation
Indicates that something exists, occurs, or is located at a particular elevation or height above a reference level.
-
E.
elevation
Indicates the vertical height or altitude of one entity relative to a reference level or another entity.
- 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_69d6aa5e51e8819095f06881cecf152e |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d711b5dd8c81908f1d9b126e4c3ae7 |
completed | April 9, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69d6f30df9948190ab3cdc33977fac14 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:15 p.m.