Triple
T25475089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grail |
E638409
|
entity |
| Predicate | systemNATOReportingNameFor |
P158039
|
FINISHED |
| Object | SA-7 Grail |
—
|
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: SA-7 Grail | Statement: [Grail, systemNATOReportingNameFor, SA-7 Grail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: systemNATOReportingNameFor Context triple: [Grail, systemNATOReportingNameFor, SA-7 Grail]
-
A.
natoReportingNameOfSystem
chosen
Indicates that one entity is the NATO reporting name assigned to a particular military system.
-
B.
natoEquivalent
Indicates that one entity is the counterpart or functional equivalent of another within the NATO (North Atlantic Treaty Organization) framework.
-
C.
NATOcode
Indicates that there is a specified NATO (North Atlantic Treaty Organization) code assigned to or associated with an entity.
-
D.
NATOReportingNameOfVariant
Indicates that one entity is the NATO reporting name assigned specifically to a variant of another entity (typically a military system or equipment).
-
E.
natoReportingNameOfBaseAircraft
Indicates that one entity is the NATO reporting name assigned to the other entity, which is the original (base) aircraft model.
- 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_69e75db9b964819096802dcf502e577e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 21, 2026, 2:25 p.m.