Triple
T28551322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Felix Baumgartner |
E722891
|
entity |
| Predicate | reachedSpeed |
P12248
|
FINISHED |
| Object | faster than the speed of sound |
—
|
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: faster than the speed of sound | Statement: [Felix Baumgartner, reachedSpeed, faster than the speed of sound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reachedSpeed Context triple: [Felix Baumgartner, reachedSpeed, faster than the speed of sound]
-
A.
speedAchieved
chosen
Indicates that a particular speed has been reached or attained by an entity during an event or action.
-
B.
plannedSpeed
Indicates the intended or target speed that an entity is expected or scheduled to maintain, rather than its actual current speed.
-
C.
currentSpeed
Indicates the present rate at which an entity is moving over time.
-
D.
maxSpeed
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
-
E.
hasSpeedRegime
Indicates a relationship where an entity is associated with a particular speed range or operating speed condition under which it functions or is evaluated.
- 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_69f01a60204481909af1bb76247b8221 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 3:42 a.m.