Triple
T4637341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bell X-1B |
E101563
|
entity |
| Predicate | hasNoseDesign |
P20675
|
FINISHED |
| Object | pointed nose for supersonic flight |
—
|
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: pointed nose for supersonic flight | Statement: [Bell X-1B, hasNoseDesign, pointed nose for supersonic flight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoseDesign Context triple: [Bell X-1B, hasNoseDesign, pointed nose for supersonic flight]
-
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.
hasDesign
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
-
D.
hasColorOfNose
Indicates that one entity possesses a nose whose color matches or is characterized by the specified color entity.
-
E.
hasDesignOption
Indicates that an entity is associated with or offers a particular design alternative or configurable design choice.
- 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_69bd43d2f1c081908cd4b7ec48ecc73d |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a62a9e48190b0cf1cbcc51f00c0 |
completed | March 20, 2026, 2:32 p.m. |
| PD | Predicate disambiguation | batch_69bd5233cb5081908807e2b150f0ca06 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:13 p.m.