Triple
T4206089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commander of the Bryansk Front |
E93783
|
entity |
| Predicate | rankOfOfficeHolder |
P32760
|
FINISHED |
| Object | army general |
—
|
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: army general | Statement: [Commander of the Bryansk Front, rankOfOfficeHolder, army general]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankOfOfficeHolder Context triple: [Commander of the Bryansk Front, rankOfOfficeHolder, army general]
-
A.
rankHeldByOfficeholder
chosen
Indicates the specific rank or level associated with an office or position that is held by a particular officeholder.
-
B.
officeHolderOf
Indicates that a person holds or has held an official position or role within a specified organization, institution, or office.
-
C.
officeHolderRoleFor
Indicates that a specific role or position is held by an office holder within an organization or governing body.
-
D.
ordinalInOffice
Indicates the numerical order or rank of an individual’s term or tenure in a particular office or position.
-
E.
officeHolderTitle
Indicates the official position or title held by a person in an office or role.
- 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_69b3451743608190808f41d17ccf2650 |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b34e098da881909a0cc339cc186627 |
completed | March 12, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69b347efd9b08190bb50f82e4e7fe06d |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:03 p.m.