Triple
T37784908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 満州戦線 |
E941925
|
entity |
| Predicate | 背景 |
P43371
|
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.
context
Indicates that one entity provides the surrounding circumstances, setting, or background within which another entity, event, or statement occurs or is interpreted.
-
B.
backgroundEvent
Indicates that one event occurs in the background relative to another primary or foreground event.
-
C.
socialBackground
Indicates a relationship where one entity’s social origin, class, or upbringing context is associated with or characterizes another entity.
-
D.
historicalBackground
chosen
Indicates that one entity provides contextual historical information or circumstances that help explain the origin, development, or significance of another entity.
-
E.
backgroundMeaning
Indicates that one entity provides contextual or underlying information that influences the interpretation or significance of another entity.
- 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_69f76ee5cb0c81909a363d1c929156c0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.