Triple
T6831953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Fork Canyon |
E157157
|
entity |
| Predicate | entranceElevationApprox |
P55629
|
FINISHED |
| Object | about 5,000 feet above sea level |
—
|
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: about 5,000 feet above sea level | Statement: [American Fork Canyon, entranceElevationApprox, about 5,000 feet above sea level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entranceElevationApprox Context triple: [American Fork Canyon, entranceElevationApprox, about 5,000 feet above sea level]
-
A.
elevationApproxMeters
Indicates the approximate elevation of an entity above sea level, measured in meters.
-
B.
elevationFeetApproximate
chosen
Indicates the approximate elevation of an entity above sea level, measured in feet.
-
C.
entranceWidth
Indicates the measured horizontal span of an entrance opening that defines how wide the entry passage is.
-
D.
numberOfBasementLevels
Indicates the total count of basement levels associated with a given structure or property.
-
E.
hasLowerFloor
Indicates that one location, structure, or level includes or is directly connected to a floor situated below another floor.
- 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_69c6882a5b5c8190917a7db9ed36bad1 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d62992908190996efab71cbf70f0 |
completed | March 27, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69c6d09d95f0819091ca7f897dc21efe |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:18 p.m.