Triple
T8556154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jakt, Attack och Spaning 39 |
E202567
|
entity |
| Predicate | roleCombination |
P28456
|
FINISHED |
| Object | air-to-air combat |
—
|
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: air-to-air combat | Statement: [Jakt, Attack och Spaning 39, roleCombination, air-to-air combat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleCombination Context triple: [Jakt, Attack och Spaning 39, roleCombination, air-to-air combat]
-
A.
roleDependsOn
Indicates that the existence, behavior, or permissions of one role are contingent upon or derived from another role.
-
B.
roleWithCEP
Indicates that an entity holds a specific role or function that is associated with a defined Contextualized Event or Process (CEP).
-
C.
connectsRole
Indicates a relationship in which one entity is linked to another by assigning or associating a specific role between them.
-
D.
roleOfGroup
Indicates the function, responsibility, or position that a group holds within a broader context or structure.
-
E.
possibleRole
chosen
Indicates that an entity is capable of or eligible to serve in a particular role or function in a given 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_69ca832610e08190b3b6c6cd2c250255 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe88bcce081909e12e4037a0e6323 |
completed | March 31, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69cbd1160fcc8190aa380a73610af731 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:19 p.m.