Triple
T8465262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nomonhan area |
E200145
|
entity |
| Predicate | majorConflictDate |
P40469
|
FINISHED |
| Object | 1939 |
—
|
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: 1939 | Statement: [Nomonhan area, majorConflictDate, 1939]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorConflictDate Context triple: [Nomonhan area, majorConflictDate, 1939]
-
A.
majorConflictYear
chosen
Indicates the year in which a major conflict, such as a war or large-scale violent confrontation, took place or reached a defining point.
-
B.
conflictPeriod
Indicates the time span during which a particular conflict or dispute is occurring or in effect between the related entities.
-
C.
hasMonthOfConflict
Indicates that a conflict is associated with, occurs in, or is characterized by a specific calendar month.
-
D.
conflictStartTime
Indicates the specific point in time at which a conflict between entities begins.
-
E.
mainConflict
Indicates the primary opposing force, problem, or struggle that drives tension and narrative progression between entities or sides.
- 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_69ca83198c4c8190a337bf717d1813f5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4d05b2881909bddf58df0ee1143 |
completed | March 31, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_69cbd10072cc819084be1ed9ac7ebe9d |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:11 p.m.