Triple
T9335476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benelux armed forces |
E224631
|
entity |
| Predicate | cooperationLevel |
P63518
|
FINISHED |
| Object | high interoperability |
—
|
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: high interoperability | Statement: [Benelux armed forces, cooperationLevel, high interoperability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cooperationLevel Context triple: [Benelux armed forces, cooperationLevel, high interoperability]
-
A.
cooperatingLevel
chosen
Indicates the degree or intensity to which two or more entities are working together toward a shared goal or activity.
-
B.
cooperationType
Indicates the specific kind or form of cooperative relationship that exists between the related entities.
-
C.
cooperateThrough
Indicates that entities work together or coordinate their actions by means of a specific intermediary, method, or channel.
-
D.
isCooperative
Indicates that an entity engages willingly and constructively in joint actions or relationships with others, working together toward shared goals.
-
E.
hasCooperative
Indicates that one entity participates in a cooperative relationship or partnership with another entity.
- 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_69ca84286fcc81909f6e7fd7a7e862a2 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd37f031888190a90d263d225d163c |
completed | April 1, 2026, 3:21 p.m. |
| PD | Predicate disambiguation | batch_69cc7a66aef08190b8d668cff5b04f5f |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:40 p.m.