Triple
T804640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bell X-1 |
E17401
|
entity |
| Predicate | brokeSoundBarrierAltitude |
P21220
|
FINISHED |
| Object | approximately 45,000 ft |
—
|
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 45,000 ft | Statement: [Bell X-1, brokeSoundBarrierAltitude, approximately 45,000 ft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brokeSoundBarrierAltitude Context triple: [Bell X-1, brokeSoundBarrierAltitude, approximately 45,000 ft]
-
A.
altitudeOfRecordFlight
Indicates the altitude reached during a particular record-setting flight.
-
B.
explosionAltitude
Indicates the height above a reference surface at which an explosion occurs or is triggered.
-
C.
hasAltitudeOfDetonation
Indicates that an explosive event or detonation occurs at a specified altitude above a reference level (typically ground or sea level).
-
D.
altitudeCapability
Indicates the maximum or typical altitude at which an entity can effectively operate or function.
-
E.
brokeGround
Indicates that an entity initiated construction or development on a site, typically by starting physical work such as excavation or foundation laying.
- 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_69a4937ae8a08190b5084a03d532b30e |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4ace495348190aec66f35ea90bc89 |
completed | March 1, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69a4aa70973c8190adbf08302d1103a9 |
completed | March 1, 2026, 9:06 p.m. |
| PDg | Predicate description generation | batch_69a4ace369b481908ad69de6de99f5e6 |
completed | March 1, 2026, 9:17 p.m. |
Created at: March 1, 2026, 7:38 p.m.