Triple
T20100390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maizuru Naval Base |
E496516
|
entity |
| Predicate | roleDuringPeacetime |
P7158
|
FINISHED |
| Object | maritime security operations |
—
|
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: maritime security operations | Statement: [Maizuru Naval Base, roleDuringPeacetime, maritime security operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleDuringPeacetime Context triple: [Maizuru Naval Base, roleDuringPeacetime, maritime security operations]
-
A.
peacetimeRole
chosen
Indicates the role, function, or duties an entity holds during periods of peace rather than during wartime or conflict.
-
B.
militaryRole
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
C.
formerMilitaryRole
Indicates that an entity previously held, but no longer holds, a specific military role or position.
-
D.
servedInRole
Indicates that one entity performed duties or held a position within a specified role or office in relation to another entity.
-
E.
roleDuringOccupation
Indicates the specific role or position an entity held during a particular occupation or period of control.
- 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_69da626eee3881909f3454986d4a6511 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6666ff4008190ae1eec907c89bd3b |
completed | April 20, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69e54cf788188190a46cc49c9ce7617f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:26 p.m.