Triple
T29656750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mongolia–Manchukuo border |
E750288
|
entity |
| Predicate | yearOfMajorClashes |
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: [Mongolia–Manchukuo border, yearOfMajorClashes, 1939]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfMajorClashes Context triple: [Mongolia–Manchukuo border, yearOfMajorClashes, 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.
startOfMajorConflict
Indicates that one event marks the beginning or initial outbreak of a major conflict between parties.
-
C.
numberOfMajorBattles
Indicates the total count of significant or major battles associated with an entity or event.
-
D.
conflictBeganInYear
Indicates that the specified conflict started or first broke out in the given calendar year.
-
E.
yearInConflict
Indicates the specific year or years during which a given conflict took place or was actively ongoing.
- 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: April 28, 2026, 6:55 p.m.