Triple
T13693068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fishbed |
E328313
|
entity |
| Predicate | appliesToSpeedClass |
P1129
|
FINISHED |
| Object | supersonic aircraft |
—
|
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 aircraft | Statement: [Fishbed, appliesToSpeedClass, supersonic aircraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToSpeedClass Context triple: [Fishbed, appliesToSpeedClass, supersonic aircraft]
-
A.
speedClass
Indicates the categorical speed level or range assigned to an entity based on how fast it moves or operates.
-
B.
appliedToVehicleType
Indicates that something (such as a rule, restriction, or condition) is specifically applicable to a particular type or category of vehicle.
-
C.
designedServiceSpeed
Indicates the intended or specified operational speed at which a service is designed to function.
-
D.
appliesTo
chosen
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
E.
requiresSpeed
Indicates that an entity needs to be performed, operated, or handled at or above a certain speed in order to be valid or effective.
- 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc8757b648190a26181efbad09a43 |
completed | April 12, 2026, 4:29 p.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:54 p.m.