Triple
T1580922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expeditionary Strike Group |
E33759
|
entity |
| Predicate | alliedEquivalent |
P22333
|
FINISHED |
| Object | NATO amphibious task group |
—
|
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: NATO amphibious task group | Statement: [Expeditionary Strike Group, alliedEquivalent, NATO amphibious task group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alliedEquivalent Context triple: [Expeditionary Strike Group, alliedEquivalent, NATO amphibious task group]
-
A.
historicallyAlliedWith
Indicates that two entities have been political, military, or strategic allies during some period in the past.
-
B.
alliedUnit
chosen
Indicates that one unit is associated as an ally or cooperative partner with another unit, typically sharing goals or working together.
-
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.
alliesInWar
Indicates that two or more parties are cooperating as allies on the same side in a specific war or armed conflict.
- 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_69a885f27a4c8190a4622252cdf54c00 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abacfb1144819080c5687175aba1e1 |
completed | March 7, 2026, 4:43 a.m. |
| PD | Predicate disambiguation | batch_69aa61b0f5bc8190b1dc272990a59c13 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:27 p.m.