Triple
T32716571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Awana Skyway |
E836535
|
entity |
| Predicate | altitudeChange |
P6813
|
FINISHED |
| Object | significant elevation gain from mid-hill to mountaintop |
—
|
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: significant elevation gain from mid-hill to mountaintop | Statement: [Awana Skyway, altitudeChange, significant elevation gain from mid-hill to mountaintop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: altitudeChange Context triple: [Awana Skyway, altitudeChange, significant elevation gain from mid-hill to mountaintop]
-
A.
elevationChange
chosen
Indicates a change in vertical position or altitude between two points or states.
-
B.
altitudeEffect
Indicates how a change in altitude influences or modifies some property, condition, or outcome.
-
C.
elevation
Indicates the vertical height or altitude of one entity relative to a reference level or another entity.
-
D.
altitudeProfile
Indicates the variation of elevation or height along a path, route, or trajectory over distance or time.
-
E.
altitudeOptimization
Indicates optimizing the height or elevation at which an entity operates or is positioned to achieve better performance or efficiency.
- 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_69f34935455881909088975d79460418 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6cd126fcc8190aa1f1f146e45ec0c |
completed | May 3, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:11 a.m.