Triple
T6378053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Netherlands Mine Countermeasures Service |
E143512
|
entity |
| Predicate | typeOfMinesHandled |
P6074
|
FINISHED |
| Object | moored mines |
—
|
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: moored mines | Statement: [Netherlands Mine Countermeasures Service, typeOfMinesHandled, moored mines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfMinesHandled Context triple: [Netherlands Mine Countermeasures Service, typeOfMinesHandled, moored mines]
-
A.
typicalOrdnance
Indicates that something is a standard or commonly used type of weaponry or munitions associated with a given entity or context.
-
B.
hadLandmines
Indicates that one entity possessed, contained, or was equipped with landmines in relation to another entity or context.
-
C.
hasDrillHolesFrom
Indicates that an object bears drill holes that were created by another specified entity or process.
-
D.
ammunitionType
chosen
Indicates the specific kind or category of ammunition associated with or used by an entity.
-
E.
specialForcesInvolved
Indicates that special forces units participate in or are involved in the referenced action, event, or operation.
- 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_69c008d9f4348190ab598a2913259a1c |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0683ed0788190b00f626c76a71ea2 |
completed | March 22, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69c060eff524819094cee1c70a0c1ff4 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:33 p.m.