Triple
T14832998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Betty Ford Alpine Gardens |
E348755
|
entity |
| Predicate | locatedAtHighAltitude |
P73807
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Betty Ford Alpine Gardens, locatedAtHighAltitude, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedAtHighAltitude Context triple: [Betty Ford Alpine Gardens, locatedAtHighAltitude, true]
-
A.
locatedAtAltitude
Indicates that an entity exists or is positioned at a specific height above a reference level, typically sea level.
-
B.
isHighElevation
chosen
Indicates that an entity is located at or associated with a relatively high altitude or elevation above a reference level, typically sea level.
-
C.
usedHighAltitudePorters
Indicates that an entity employed porters specifically for work or transport at high altitudes.
-
D.
grownAtHighElevation
Indicates that something is cultivated or produced in locations situated at relatively high altitudes above sea level.
-
E.
altitudeEffect
Indicates how a change in altitude influences or modifies some property, condition, or outcome.
- 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_69d822ec69008190a9232caa68836872 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded075af0881908fb35a9e7ee46749 |
completed | April 14, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69de8c13418c819088ff9905ace1416a |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:52 a.m.