Triple
T27032181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian Caucasus Army |
E680947
|
entity |
| Predicate | frontNameInWorldWarI |
P165067
|
FINISHED |
| Object | Caucasus Front |
—
|
NE NERFINISHED |
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: Caucasus Front | Statement: [Russian Caucasus Army, frontNameInWorldWarI, Caucasus Front]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frontNameInWorldWarI Context triple: [Russian Caucasus Army, frontNameInWorldWarI, Caucasus Front]
-
A.
roleInWorldWarI
Indicates the specific function, position, or involvement an entity had during World War I.
-
B.
frontDuringWWII
Indicates that an entity served as a military front or active combat theater during World War II.
-
C.
positionOnWorldWarI
Indicates a person’s or group’s stance, opinion, or policy regarding World War I.
-
D.
worldWarTwoNames
Indicates that the entities are alternative names, titles, or designations referring to World War II.
-
E.
worldWarIRecognition
Indicates formal acknowledgment or commemoration of involvement, service, or impact related to World War I.
- F. None of above. chosen
Provenance (4 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_69eeeb5566f08190813daf896fa3da04 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f65705a3048190a3728b695ba2ae65 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69f6562ef4e4819082ce6abd41b74dc5 |
completed | May 2, 2026, 7:53 p.m. |
Created at: April 27, 2026, 7:14 a.m.