Triple
T16888856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2nd Guards Tank Army |
E421610
|
entity |
| Predicate | gainedGuardsTitle |
P124862
|
FINISHED |
| Object | 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: 1943 | Statement: [2nd Guards Tank Army, gainedGuardsTitle, 1943]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gainedGuardsTitle Context triple: [2nd Guards Tank Army, gainedGuardsTitle, 1943]
-
A.
titleDefendedBy
Indicates that a specific title or championship is actively defended or held against challengers by a particular entity.
-
B.
guard
Indicates that one entity protects, watches over, or defends another entity or resource from harm, intrusion, or unauthorized access.
-
C.
guardian
Indicates a protective or custodial relationship in which one entity is responsible for the care, safety, or oversight of another.
-
D.
guardType
Indicates the specific kind or category of guarding role or protection associated with an entity.
-
E.
protectedBy
Indicates that one entity provides protection, defense, or safeguarding for another entity.
- 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_69d889d470fc8190b4aec199636c0c56 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3bbc2f6d081909c76fa2a6b87e083 |
completed | April 18, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69e32b90ec3c819099c51bb7baf2984c |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e32e2c07b081908c8fee9f5507bb9e |
completed | April 18, 2026, 7:09 a.m. |
Created at: April 10, 2026, 5:29 a.m.