Triple
T1075288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | X-59 QueSST |
E23821
|
entity |
| Predicate | noseDesign |
P20675
|
FINISHED |
| Object | long slender nose to shape shock waves |
—
|
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: long slender nose to shape shock waves | Statement: [X-59 QueSST, noseDesign, long slender nose to shape shock waves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: noseDesign Context triple: [X-59 QueSST, noseDesign, long slender nose to shape shock waves]
-
A.
noseType
chosen
Indicates the specific shape or classification of a nose that an entity possesses.
-
B.
noseGearFeature
Indicates that there is a specific characteristic, component, or design attribute associated with the nose landing gear of an aircraft.
-
C.
noseGearOrigin
Indicates the point or location from which the nose landing gear of an aircraft extends or is mounted.
-
D.
hasDesign
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
-
E.
designedIn
Indicates that something was created, planned, or conceived during a particular time period or at a specific location.
- 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_69a493f1ddf48190a99d54b00e99f8ce |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b92e480c81909a848b48c196a293 |
completed | March 1, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69a4b73ba8208190be7f3cef8c18689b |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.