Triple
T37784889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 満州戦線 |
E941925
|
entity |
| Predicate | 主な戦闘地域 |
P146580
|
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.
placeOfMainEngagement
Indicates the primary location where an entity carries out its main activities, operations, or engagements.
-
B.
primaryBattlefieldOf
chosen
Indicates that a specified location serves as the main or most significant battlefield where a particular conflict or war primarily took place.
-
C.
主な出店地域
Indicates the primary geographic areas or regions where an entity mainly opens or operates its stores or outlets.
-
D.
combatArea
Indicates a designated location or zone where combat or fighting activities take place or are authorized.
-
E.
mainBattle
Indicates that one battle is the primary or most significant engagement associated with a particular conflict, campaign, or 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.