Triple
T17121354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brian Binnie |
E415472
|
entity |
| Predicate | altitudeRecord |
P126051
|
FINISHED |
| Object | 112000 meters (approximate) on SpaceShipOne Flight 17P |
—
|
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: 112000 meters (approximate) on SpaceShipOne Flight 17P | Statement: [Brian Binnie, altitudeRecord, 112000 meters (approximate) on SpaceShipOne Flight 17P]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: altitudeRecord Context triple: [Brian Binnie, altitudeRecord, 112000 meters (approximate) on SpaceShipOne Flight 17P]
-
A.
highestPoint
Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined area.
-
B.
peakElevationMetres
Indicates the maximum height of an entity above sea level, measured in metres.
-
C.
areaPeak
Indicates that a specified location or region is the highest point (peak) within a given area or spatial extent.
-
D.
highestPassApproxElevation
Indicates the approximate elevation of the highest pass along a given route or within a specified area.
-
E.
highestPeakClimbed
Indicates the tallest mountain or peak that an entity has successfully climbed.
- F. None of above. chosen
Provenance (4 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_69d886d090cc8190a39cb94992586905 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3e809ee888190a2cf69d59c0b9c20 |
completed | April 18, 2026, 8:22 p.m. |
| PD | Predicate disambiguation | batch_69e35d6d20808190a38bb32e2294bc48 |
completed | April 18, 2026, 10:31 a.m. |
| PDg | Predicate description generation | batch_69e37542d060819082aa73948eb8ebd4 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:36 a.m.