Triple
T3072306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mikoyan-Gurevich MiG-15 |
E64051
|
entity |
| Predicate | trainerVariantNATOReportingName |
P6062
|
FINISHED |
| Object | Midget |
—
|
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: Midget | Statement: [Mikoyan-Gurevich MiG-15, trainerVariantNATOReportingName, Midget]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trainerVariantNATOReportingName Context triple: [Mikoyan-Gurevich MiG-15, trainerVariantNATOReportingName, Midget]
-
A.
isMilitaryVariantOf
Indicates that one entity is a military-specific version or adaptation of another, typically civilian or general-purpose, entity.
-
B.
crewVariantName
Indicates the specific name or label assigned to a particular variant or version of a crew configuration.
-
C.
NATOcode
chosen
Indicates that there is a specified NATO (North Atlantic Treaty Organization) code assigned to or associated with an entity.
-
D.
hasMilitaryDesignation
Indicates that an entity is assigned a specific military-related code, title, or classification.
-
E.
positionOnNATO
Indicates a country's stance or alignment regarding membership in, support for, or opposition to NATO.
- 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_69ad857a8aec8190bfdfd9c14554ac5a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada14c8bd881909cf1bb2649ba36db |
completed | March 8, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69ad9625b30c819099ef9349c91d7b25 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:02 p.m.