Triple
T23719895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Missile With a Man in It |
E586110
|
entity |
| Predicate | associatedWithWingDesign |
P7143
|
FINISHED |
| Object | very small, thin wings |
—
|
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: very small, thin wings | Statement: [The Missile With a Man in It, associatedWithWingDesign, very small, thin wings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithWingDesign Context triple: [The Missile With a Man in It, associatedWithWingDesign, very small, thin wings]
-
A.
architectOfWing
Indicates that one entity served as the architect responsible for designing a particular wing of a building or structure.
-
B.
hasWingIn
Indicates that an entity possesses a wing that is located in or contained within another specified entity or structure.
-
C.
hasWingOf
Indicates that one entity possesses or is associated with the wing that belongs to another entity.
-
D.
hasWingConfiguration
chosen
Indicates how an entity’s wings are arranged, structured, or configured relative to its body or to each other.
-
E.
wingOf
Indicates that something is a wing that forms a physical or functional part of another entity.
- 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.