Triple
T19057885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bell X-1A |
E466445
|
entity |
| Predicate | brokeSpeedRecord |
P42667
|
FINISHED |
| Object | 1953-12-12 |
—
|
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: 1953-12-12 | Statement: [Bell X-1A, brokeSpeedRecord, 1953-12-12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brokeSpeedRecord Context triple: [Bell X-1A, brokeSpeedRecord, 1953-12-12]
-
A.
brokeRecord
chosen
Indicates that one entity surpassed a previous best performance or achievement standard set by another (or itself) in a given domain.
-
B.
brokeRecordOf
Indicates that one entity has surpassed or exceeded a previous performance or achievement previously held by another entity.
-
C.
maximumSpeedRecord
Indicates that an entity holds the highest recorded speed value (a speed record) within a given context or category.
-
D.
brokeSoundBarrier
Indicates that an entity achieved a speed exceeding the speed of sound, thereby breaking the sound barrier.
-
E.
peacetimeSpeedRecord
Indicates the maximum speed achieved under non-combat, peacetime conditions, recognized as a record.
- 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_69d8dd040fb881909af2a964f65ad208 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5dc0742288190a594be859184841a |
completed | April 20, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69e4b99633c8819097988608c278ecf8 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:03 p.m.