Triple
T689107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial Russian Army |
E13350
|
entity |
| Predicate | problems |
P18260
|
FINISHED |
| Object | logistical difficulties |
—
|
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: logistical difficulties | Statement: [Imperial Russian Army, problems, logistical difficulties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: problems Context triple: [Imperial Russian Army, problems, logistical difficulties]
-
A.
issues
Indicates that an entity formally produces, releases, or distributes something, such as a document, order, or resource, making it officially available.
-
B.
problemStatement
Indicates that an entity presents, defines, or expresses a specific problem or issue to be addressed.
-
C.
proposes
Indicates that one entity formally suggests or puts forward an idea, plan, or course of action to another entity for consideration or approval.
-
D.
issue
Indicates that an entity formally publishes, releases, or distributes something, such as a document, statement, or item, often in an official or authoritative capacity.
-
E.
fault
Indicates that one entity is responsible or at blame for a problem, error, or undesirable outcome involving another entity or situation.
- 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_69a4933e0f98819097d22766c49b61b8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a0f55f7481909e052a25bd12d455 |
completed | March 1, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69a49d2048d48190ab99ab59accb6909 |
completed | March 1, 2026, 8:10 p.m. |
| PDg | Predicate description generation | batch_69a4a0f405748190ba72a9cfe946a8ec |
completed | March 1, 2026, 8:26 p.m. |
Created at: March 1, 2026, 7:36 p.m.