Triple
T9849321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1st Far Eastern Front |
E239423
|
entity |
| Predicate | startOfCombatOperations |
P70447
|
FINISHED |
| Object | 1945-08-09 |
—
|
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: 1945-08-09 | Statement: [1st Far Eastern Front, startOfCombatOperations, 1945-08-09]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startOfCombatOperations Context triple: [1st Far Eastern Front, startOfCombatOperations, 1945-08-09]
-
A.
startOfDefense
Indicates the point in time or event at which a defense or defensive action begins.
-
B.
combatDebut
Indicates the event or moment when an entity first participates in combat or a fight.
-
C.
introducedToCombat
Indicates that something was brought into use or implemented specifically for the purpose of addressing or mitigating a particular problem, threat, or undesirable condition.
-
D.
firstCombatOperation
chosen
Indicates that the referenced combat operation is the earliest or initial combat action undertaken by the entity in question.
-
E.
offensiveOperation
Indicates an action or campaign in which a party actively initiates hostile or military measures against an opponent.
- 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_69ca84e4fdc08190a624425bcef98665 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb371894c8190971ba497a2801521 |
completed | April 2, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69cd03e57cac8190914bb5ae608a6e0e |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:34 p.m.