Triple
T33412836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fiddler |
E855634
|
entity |
| Predicate | introducedAsNATOReportingName |
P112364
|
FINISHED |
| Object | 1960s |
—
|
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: 1960s | Statement: [Fiddler, introducedAsNATOReportingName, 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedAsNATOReportingName Context triple: [Fiddler, introducedAsNATOReportingName, 1960s]
-
A.
introducedAsNATOReportingNameFor
Indicates that one entity was designated and announced as the official NATO reporting name for another entity.
-
B.
natoReportingNameOfSystem
Indicates that one entity is the NATO reporting name assigned to a particular military system.
-
C.
natoReportingNameOfBaseAircraft
Indicates that one entity is the NATO reporting name assigned to the other entity, which is the original (base) aircraft model.
-
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.
aircraftNamedNATOCode
chosen
Indicates that an aircraft is designated or referred to by a specific NATO reporting name or code.
- 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fdb31800508190beec15adb9bbd292 |
completed | May 8, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69fdb19c381c8190bafb2f565da097f1 |
completed | May 8, 2026, 9:49 a.m. |
Created at: May 1, 2026, 1:36 a.m.