Triple
T21748044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 関東軍司令官 |
E536836
|
entity |
| Predicate | 関連国家 |
P835
|
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.
relatedCountry
chosen
Indicates that there is a relevant or associated relationship between an entity and a specified country, without specifying the exact nature of that relationship.
-
B.
politicalRelation
Indicates a relationship between entities that involves political alignment, influence, affiliation, conflict, or cooperation within a political context.
-
C.
diplomaticRelationBetween
Indicates the existence of a formal diplomatic relationship or ties between two political entities or states.
-
D.
involvedCountry
Indicates that a country participates in, is associated with, or is otherwise implicated in the referenced event, activity, or situation.
-
E.
worldRelationship
Indicates a broad, often high-level connection or interaction that exists between entities within a global or world-scale context.
- 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_69e0c46eab808190b848242d63a17c47 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f01a77e19c81909bf26f96aa41a7ce |
completed | April 28, 2026, 2:24 a.m. |
| PD | Predicate disambiguation | batch_69e6969c16fc8190b5126c169317d85d |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:50 p.m.