Triple
T3724079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saab 37 Viggen |
E81705
|
entity |
| Predicate | SH 37 ViggenRole |
P50367
|
FINISHED |
| Object | maritime reconnaissance and strike |
—
|
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: maritime reconnaissance and strike | Statement: [Saab 37 Viggen, SH 37 ViggenRole, maritime reconnaissance and strike]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SH 37 ViggenRole Context triple: [Saab 37 Viggen, SH 37 ViggenRole, maritime reconnaissance and strike]
-
A.
fighter1
Indicates that the subject is the first participant or primary combatant in a fight or competitive physical confrontation.
-
B.
fighter2
Indicates that the subject is the second participant (opponent) in a fighting or combat relationship or event.
-
C.
testAircraftRole
chosen
Indicates that an aircraft is assigned or evaluated for a specific operational role or function.
-
D.
mainFighterAircraft
Indicates that an aircraft serves as the primary fighter aircraft for a given country, organization, or military force.
-
E.
Tu-95MSRole
Indicates the specific operational role or mission type assigned to the Tu-95MS aircraft within its usage or deployment context.
- 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_69ad8b1b7ef081908d2d381bbf54985a |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcaf3f2ec8190a3a8f363cfb762f3 |
completed | March 8, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69adc0452f5081909c79e114a86cce8c |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.