Triple
T24292467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skyflash |
E605860
|
entity |
| Predicate | introducedAsImprovementOf |
P47073
|
FINISHED |
| Object | AIM-7E Sparrow |
—
|
NE NERFINISHED |
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: AIM-7E Sparrow | Statement: [Skyflash, introducedAsImprovementOf, AIM-7E Sparrow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedAsImprovementOf Context triple: [Skyflash, introducedAsImprovementOf, AIM-7E Sparrow]
-
A.
improvesOn
Indicates that one entity enhances, refines, or performs better than another entity, typically by addressing its limitations or increasing its effectiveness.
-
B.
hasImproved
Indicates that an entity’s state, quality, or performance has become better compared to a previous point in time.
-
C.
upgradeOf
chosen
Indicates that one entity is a newer, improved, or more advanced version of another entity.
-
D.
developedAsReplacementFor
Indicates that one entity was created or designed specifically to take the place of another entity, serving as its successor or substitute.
-
E.
developedAsReactionTo
Indicates that one entity was created, formed, or evolved specifically in response to the existence, influence, or impact 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_69e29549335881909cbf27adcaba1cf0 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f29157840c81908da157e93ad21527 |
completed | April 29, 2026, 11:16 p.m. |
| PD | Predicate disambiguation | batch_69f1c45c6ec081908401b69424428100 |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 12:09 a.m.