Triple
T8914646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Standing NATO Mine Countermeasures Group 1 |
E212266
|
entity |
| Predicate | permanent |
P32534
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Standing NATO Mine Countermeasures Group 1, permanent, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: permanent Context triple: [Standing NATO Mine Countermeasures Group 1, permanent, true]
-
A.
permanence
chosen
Indicates that a state, condition, or relationship continues to hold over time without significant change or interruption.
-
B.
permanentAdoption
Indicates a lasting, legally recognized adoption relationship in which the adoptee becomes a permanent member of the adopter’s family.
-
C.
committed
Indicates that an agent has carried out or been responsible for a specific act, event, or wrongdoing.
-
D.
constant
Indicates that the relationship or value does not change across different instances, contexts, or over time.
-
E.
perpetuates
Indicates that one entity causes a state, condition, or situation involving another entity to continue or persist over time.
- 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_69ca8393b1808190bd4336787ffa2c40 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc660e620c8190b02b9843c8f02bfa |
completed | April 1, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69cc5ecf55248190a29f00fbf99f13c4 |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:56 p.m.