Triple
T26458026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bedok-class mine countermeasures vessel |
E665545
|
entity |
| Predicate | navalWarfareArea |
P77974
|
FINISHED |
| Object | mine warfare |
—
|
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: mine warfare | Statement: [Bedok-class mine countermeasures vessel, navalWarfareArea, mine warfare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalWarfareArea Context triple: [Bedok-class mine countermeasures vessel, navalWarfareArea, mine warfare]
-
A.
marineAreaShare
Indicates the proportion of a larger marine area that is occupied, controlled, or otherwise attributed to a specific entity.
-
B.
marineArea
Indicates a relationship where an entity is located in, associated with, or relevant to a specific marine or oceanic area.
-
C.
nauticalRegion
Indicates that one entity is a maritime or nautical area within which the other entity is located, operates, or is relevant.
-
D.
navalOperations
chosen
Indicates involvement in planning, conducting, or supporting military activities carried out by naval forces at sea or from the sea.
-
E.
navalOperationsBy
Indicates that a set of naval operations is conducted, controlled, or carried out by a specified agent or organization.
- 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_69ee883e812c8190a9b5a9cdb87fee5e |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 12:10 a.m.