Triple
T804639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bell X-1 |
E17401
|
entity |
| Predicate | brokeSoundBarrierMachNumber |
P12248
|
FINISHED |
| Object | 1.06 |
—
|
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: 1.06 | Statement: [Bell X-1, brokeSoundBarrierMachNumber, 1.06]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brokeSoundBarrierMachNumber Context triple: [Bell X-1, brokeSoundBarrierMachNumber, 1.06]
-
A.
speedAchieved
chosen
Indicates that a particular speed has been reached or attained by an entity during an event or action.
-
B.
maxSpeed
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
-
C.
brokeGround
Indicates that an entity initiated construction or development on a site, typically by starting physical work such as excavation or foundation laying.
-
D.
breaksDownWhen
Indicates that one entity becomes nonfunctional, damaged, or fails when subjected to the presence, action, or conditions imposed by another entity.
-
E.
hasEscapeVelocity
Indicates that an object or body possesses a velocity sufficient to overcome the gravitational pull of another body without further propulsion.
- 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_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. |
Created at: March 1, 2026, 7:38 p.m.