Triple
T8914657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Standing NATO Mine Countermeasures Group 1 |
E212266
|
entity |
| Predicate | hasOperationalReadiness |
P49856
|
FINISHED |
| Object | high |
—
|
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 | Statement: [Standing NATO Mine Countermeasures Group 1, hasOperationalReadiness, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOperationalReadiness Context triple: [Standing NATO Mine Countermeasures Group 1, hasOperationalReadiness, high]
-
A.
operationalReadiness
chosen
Indicates that an entity is in a state where it is fully prepared, equipped, and able to perform its intended function or mission.
-
B.
hasOperationalComponent
Indicates that an entity includes, uses, or depends on another entity as a functional or operational part of its overall system or process.
-
C.
fullyOperationalBy
Indicates that an entity is expected or required to be completely functional and ready for use no later than a specified time or event.
-
D.
declaredFullyOperationalBy
Indicates that one entity has officially stated that another entity is completely ready and capable of functioning as intended.
-
E.
isProductionReady
Indicates that something has met all necessary quality, stability, and performance criteria to be safely deployed and used in a live production environment.
- 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.