Triple
T23719894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Missile With a Man in It |
E586110
|
entity |
| Predicate | associatedWithSpeedClass |
P9902
|
FINISHED |
| Object | supersonic |
—
|
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: supersonic | Statement: [The Missile With a Man in It, associatedWithSpeedClass, supersonic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithSpeedClass Context triple: [The Missile With a Man in It, associatedWithSpeedClass, supersonic]
-
A.
speedClass
chosen
Indicates the categorical speed level or range assigned to an entity based on how fast it moves or operates.
-
B.
associatedWithRaceCategory
Indicates a relationship in which an entity is linked or assigned to a particular race category.
-
C.
recordSpeedCategory
Indicates the classification of an entity’s speed into a predefined category (e.g., slow, normal, fast) based on its recorded speed.
-
D.
associatedWithTeamSport
Indicates a relationship where an entity is connected to, involved in, or participates in a team-based sport.
-
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_69e24906fb108190a6898751e46bdc11 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b77e2dc081908aef7a4c9b188dbd |
completed | April 29, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7 p.m.