Triple
T18654085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | siege of Orenburg |
E456014
|
entity |
| Predicate | militaryRoleOfOrenburg |
P9463
|
FINISHED |
| Object | key Russian fortress city |
—
|
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: key Russian fortress city | Statement: [siege of Orenburg, militaryRoleOfOrenburg, key Russian fortress city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryRoleOfOrenburg Context triple: [siege of Orenburg, militaryRoleOfOrenburg, key Russian fortress city]
-
A.
militaryRole
chosen
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
B.
roleAtStalingrad
Indicates the specific role, position, or function an entity held in relation to the Battle of Stalingrad.
-
C.
roleDuringRussianCivilWar
Indicates the specific function, position, or involvement an entity had during the period of the Russian Civil War.
-
D.
wasMilitaryHeadquartersOf
Indicates that a place or facility served as the main command center or headquarters for a specific military force or organization.
-
E.
formerMilitaryRole
Indicates that an entity previously held, but no longer holds, a specific military role or position.
- 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_69d8d38ea1e88190997e9b231190ba6f |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e55013997881909eee52c0a7335f4b |
completed | April 19, 2026, 9:58 p.m. |
| PD | Predicate disambiguation | batch_69e478d85864819093cbad5ed9b54878 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:47 a.m.