Triple
T21685234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 寺内内閣 |
E535212
|
entity |
| Predicate | 主要な外交問題 |
P144515
|
FINISHED |
| Object | 第一次世界大戦への対応 |
—
|
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: 第一次世界大戦への対応 | Statement: [寺内内閣, 主要な外交問題, 第一次世界大戦への対応]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 主要な外交問題 Context triple: [寺内内閣, 主要な外交問題, 第一次世界大戦への対応]
-
A.
diplomaticSignificance
Indicates the importance or impact that an event, action, or entity has within diplomatic relations between parties or states.
-
B.
hasDiplomaticDimension
chosen
Indicates that a situation, issue, or interaction involves aspects of diplomacy or international relations between entities.
-
C.
国の元首との関係
Indicates a relationship or connection that an entity has with the head of state of a country.
-
D.
internationalAffairsFunction
Indicates a functional role or responsibility related to managing, coordinating, or influencing interactions and relationships between entities across national borders.
-
E.
diplomaticPolicy
Indicates the stance, strategy, or set of guiding principles an entity adopts in managing its diplomatic relations and interactions with others.
- 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_69e0c469b6ec8190aee4cadd1527db91 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef96ca668481909f53853c7a8ea811 |
completed | April 27, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69e6968abfdc81909cf9e0bd72db9eca |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:44 p.m.