Triple
T17455741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reno Air Races |
E425022
|
entity |
| Predicate | raceAltitude |
P21269
|
FINISHED |
| Object | approximately 50 feet above ground 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: approximately 50 feet above ground level | Statement: [Reno Air Races, raceAltitude, approximately 50 feet above ground level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raceAltitude Context triple: [Reno Air Races, raceAltitude, approximately 50 feet above ground level]
-
A.
locatedAtAltitude
chosen
Indicates that an entity exists or is positioned at a specific height above a reference level, typically sea level.
-
B.
altitudeProfile
Indicates the variation of elevation or height along a path, route, or trajectory over distance or time.
-
C.
hasAltitudeFeature
Indicates that an entity possesses a characteristic or attribute related to its elevation or vertical position above a reference level.
-
D.
altitudeEffect
Indicates how a change in altitude influences or modifies some property, condition, or outcome.
-
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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e45141e1d48190b7de9159f1fd71fa |
completed | April 19, 2026, 3:51 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f0e3fc819094e466b74622c956 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:47 a.m.