Triple
T5644971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2nd Guards Tank Corps |
E124361
|
entity |
| Predicate | receivedTitleFor |
P12204
|
FINISHED |
| Object | actions at Stalingrad |
—
|
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: actions at Stalingrad | Statement: [2nd Guards Tank Corps, receivedTitleFor, actions at Stalingrad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivedTitleFor Context triple: [2nd Guards Tank Corps, receivedTitleFor, actions at Stalingrad]
-
A.
receivedTitle
chosen
Indicates that an entity has been formally granted or awarded a specific title or honor.
-
B.
providedTitle
Indicates that one entity has supplied or assigned a specific title or designation to another entity.
-
C.
titleRepresents
Indicates that a given title stands for, denotes, or symbolizes a particular concept, role, work, or entity.
-
D.
hadTitle
Indicates that an entity held or was assigned a specific title or formal designation.
-
E.
recognizesTitle
Indicates that one entity acknowledges or accepts another entity’s formal title or designation as valid or appropriate.
- 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_69c00824643c81909ffdb888a2d35189 |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c022a8eccc8190837d4705670dc25e |
completed | March 22, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69c01b2168508190b64b355cf50034ad |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:41 p.m.