Triple
T25218941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 9M38M1 |
E631906
|
entity |
| Predicate | originatingProgram |
P17523
|
FINISHED |
| Object | Buk (SA-11 Gadfly) |
—
|
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: Buk (SA-11 Gadfly) | Statement: [9M38M1, originatingProgram, Buk (SA-11 Gadfly)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originatingProgram Context triple: [9M38M1, originatingProgram, Buk (SA-11 Gadfly)]
-
A.
originProgram
chosen
Indicates the program, initiative, or source project from which an entity, item, or record originally comes.
-
B.
originatesAs
Indicates that one entity begins, arises, or comes into existence in the form, state, or role specified by another entity.
-
C.
intendedProgram
Indicates the academic or training program that an entity plans or expects to pursue, rather than one they are currently enrolled in or have completed.
-
D.
originatingService
Indicates the service from which an action, request, or piece of data was initially generated or sent.
-
E.
formerProgram
Indicates that an entity previously held the role or status of a program but no longer does so.
- 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_69e75a8d1aa48190a4320acd3654762c |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 21, 2026, 12:59 p.m.