Triple
T8536400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AN/APG-70 |
E202086
|
entity |
| Predicate | introducedForVariant |
P37905
|
FINISHED |
| Object | F-15E Strike Eagle production models |
—
|
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: F-15E Strike Eagle production models | Statement: [AN/APG-70, introducedForVariant, F-15E Strike Eagle production models]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedForVariant Context triple: [AN/APG-70, introducedForVariant, F-15E Strike Eagle production models]
-
A.
introducedFor
Indicates that one entity was presented or brought to the attention of another entity for a specific purpose or role.
-
B.
introducedForModel
chosen
Indicates that one entity was created, proposed, or brought into use specifically for application within a particular model.
-
C.
exportVariantOf
Indicates that one entity is an exported version or externally released form derived from another, original entity.
-
D.
hasVariant
Indicates that one entity exists as an alternative form, version, or variation of another entity.
-
E.
introducedFrom
Indicates that one entity was brought, originated, or caused to appear in a context, system, or environment by 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_69ca832355b08190b8b6a4ab4a4a3554 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe6a3f024819095d560a205ff1c75 |
completed | March 31, 2026, 3:22 p.m. |
| PD | Predicate disambiguation | batch_69cbd111bf988190be98c92a607c6456 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:18 p.m.