Triple
T14048103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Admiral (JMSDF) |
E338011
|
entity |
| Predicate | doctrineDomain |
P112616
|
FINISHED |
| Object | maritime defense policy of Japan |
—
|
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 defense policy of Japan | Statement: [Admiral (JMSDF), doctrineDomain, maritime defense policy of Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doctrineDomain Context triple: [Admiral (JMSDF), doctrineDomain, maritime defense policy of Japan]
-
A.
doctrineName
Indicates that one entity is the formal or recognized name of a particular doctrine associated with another entity.
-
B.
sharesDoctrine
Indicates that two entities adhere to or promote the same doctrine, belief system, or set of principles.
-
C.
doctrineType
Indicates that one entity is a classification or kind of doctrinal position, teaching, or belief system to which the other entity belongs or pertains.
-
D.
definedDoctrineAt
Indicates that a particular doctrine was formally established, articulated, or codified at a specific place or time.
-
E.
doctrineSupported
Indicates that one entity endorses, upholds, or provides backing for a particular doctrine or set of principles.
- F. None of above. chosen
Provenance (4 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_69d81c664e48819088cbd8f433aeffe5 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de3c88b5e48190b0f0149102c08992 |
completed | April 14, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69de05adef888190b023ab42ef5076b6 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de2398856c81908bed6070e4ca6ab1 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:20 p.m.