Triple
T29421101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FNS Hämeenmaa |
E746157
|
entity |
| Predicate | mineCapacity |
P13466
|
FINISHED |
| Object | over 150 naval 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: over 150 naval mines | Statement: [FNS Hämeenmaa, mineCapacity, over 150 naval mines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mineCapacity Context triple: [FNS Hämeenmaa, mineCapacity, over 150 naval mines]
-
A.
unitCapacity
Indicates the maximum quantity or load that a single unit is designed or allowed to hold, process, or accommodate.
-
B.
typicalCapacity
Indicates the usual or standard amount, volume, or capability that something is designed or expected to hold, handle, or perform under normal conditions.
-
C.
unitOfCapacity
Indicates that one entity is a unit used to measure the capacity or volume of another entity.
-
D.
annualCapacity
Indicates the maximum amount of output or throughput an entity can produce or handle within a one-year period.
-
E.
totalCapacity
chosen
Indicates the maximum amount or volume that something can hold or accommodate in total.
- 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_69f0a79f6d5c8190a350baed0157e06f |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66a68fedc8190ab94d22edc6ff90b |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 3:05 p.m.