Triple
T274807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tadeusz Bór-Komorowski |
E5222
|
entity |
| Predicate | appointed |
P8660
|
FINISHED |
| Object | Commander of the Home Army in 1943 |
—
|
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: Commander of the Home Army in 1943 | Statement: [Tadeusz Bór-Komorowski, appointed, Commander of the Home Army in 1943]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointed Context triple: [Tadeusz Bór-Komorowski, appointed, Commander of the Home Army in 1943]
-
A.
appointedAfter
Indicates that one entity was appointed to a position or role at a later time than another entity.
-
B.
appointedBy
Indicates that one entity has been formally selected or assigned to a position, role, or office by another entity.
-
C.
appointedByOffice
Indicates that an entity attains its position or role through a formal appointment made by a specific office or official authority.
-
D.
appointedFor
Indicates that an entity has been officially assigned or designated to perform a specific role, task, or function for another entity or purpose.
-
E.
nominated
Indicates that one entity formally proposes or selects another entity for a position, role, award, or recognition.
- 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_69a257e6c8788190987dfe705ca2912a |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25dd1cdf881909c2c9b77b7f88684 |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b7345c4819086c21710864a1b42 |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25c036b54819090a101c4cbdbcff7 |
completed | Feb. 28, 2026, 3:07 a.m. |
Created at: Feb. 28, 2026, 2:59 a.m.