Triple
T15137462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soviet military districts |
E361591
|
entity |
| Predicate | hadStaffElement |
P478
|
FINISHED |
| Object | military district headquarters |
—
|
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: military district headquarters | Statement: [Soviet military districts, hadStaffElement, military district headquarters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadStaffElement Context triple: [Soviet military districts, hadStaffElement, military district headquarters]
-
A.
hadStaffRole
Indicates that an entity served in a specific staff role or position for another entity during some period.
-
B.
hadMember
Indicates that an entity was formerly a member or part of another entity or group.
-
C.
hadThemeElement
Indicates that an entity includes, involves, or is characterized by a specific thematic element as part of its overall theme.
-
D.
hasGeneralStaff
Indicates that an entity has, is associated with, or is served by a general staff body responsible for overall strategic or administrative functions.
-
E.
staffIncluded
chosen
Indicates that staff members are included or provided as part of the associated entity, service, or arrangement.
- 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_69d85a06450081909c5a14ea9851a15e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e005b59b488190b0016970647e7483 |
completed | April 15, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69deb9713fe881909dec2fd3f6c84b39 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:07 a.m.