Triple
T3481006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taurus KEPD 350 |
E73488
|
entity |
| Predicate | allianceCompatibility |
P49025
|
FINISHED |
| Object | NATO-compatible weapon system |
—
|
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-compatible weapon system | Statement: [Taurus KEPD 350, allianceCompatibility, NATO-compatible weapon system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allianceCompatibility Context triple: [Taurus KEPD 350, allianceCompatibility, NATO-compatible weapon system]
-
A.
allianceType
Indicates the specific kind or category of alliance relationship that exists between entities.
-
B.
allianceStatus
Indicates the formal or informal cooperative relationship between entities, such as whether they are allies, neutral, or adversarial.
-
C.
allianceUse
Indicates that one party makes use of, benefits from, or leverages an alliance or allied relationship with another party.
-
D.
allianceSupport
Indicates a cooperative relationship where one party provides assistance, resources, or backing to an ally within the context of an alliance.
-
E.
allianceStructure
Indicates the organizational or relational configuration that defines how members of an alliance are structured and interconnected.
- F. None of above. chosen
Provenance (4 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_69ad85b3c9b08190857cae74c7f36da9 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb75850c8190ad02cf2bde8be8a7 |
completed | March 8, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69adae0935ac8190bfa8a8bd3dcd3301 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb1ecb02881908394f197e31431b4 |
completed | March 8, 2026, 5:29 p.m. |
Created at: March 8, 2026, 3:17 p.m.