Triple
T1840013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 36th Wing |
E41153
|
entity |
| Predicate | alliedCooperation |
P600
|
FINISHED |
| Object | supports operations with Japan |
—
|
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: supports operations with Japan | Statement: [36th Wing, alliedCooperation, supports operations with Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alliedCooperation Context triple: [36th Wing, alliedCooperation, supports operations with Japan]
-
A.
historicallyAlliedWith
Indicates that two entities have been political, military, or strategic allies during some period in the past.
-
B.
alliesInWar
Indicates that two or more parties are cooperating as allies on the same side in a specific war or armed conflict.
-
C.
mainAlliedPower
Indicates that an entity serves as a primary or leading ally to another entity within an alliance or coalition.
-
D.
alliedRecognition
Indicates that one entity formally acknowledges another as an ally or partner in a cooperative relationship.
-
E.
alliance
chosen
Indicates a formal cooperative relationship between entities who agree to support each other in shared goals or interests.
- 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_69a88647f9388190909bc36e795bdaec |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafd88ebc81908208394746351fe6 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.