Triple
T19220902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 山口多聞 |
E480608
|
entity |
| Predicate | 関連する国際紛争 |
P112514
|
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.
関係する国際的出来事
Indicates a relationship where something is connected to, involved in, or affected by an international event.
-
B.
関連戦争
chosen
Indicates a relationship where an entity is associated with, connected to, or involved in a particular war or military conflict.
-
C.
associatedTerritoryDispute
Indicates that there is a territorial dispute or contested claim connected to the referenced entity or relationship.
-
D.
conflictCountry
Indicates that there is an armed conflict or war involving the referenced country as a participant.
-
E.
internationalConcern
Indicates that an issue, event, or situation is regarded as significant or problematic by multiple countries or the international community as a whole.
- 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_69d8e8cb8c348190b52075823911c869 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fa3e8d488190a93fb743dabd0ffb |
completed | April 20, 2026, 10:04 a.m. |
| PD | Predicate disambiguation | batch_69e4dcf22b3c8190bee02e3af946e114 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:24 p.m.