Triple
T3082266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Battle of Kharkov |
E64284
|
entity |
| Predicate | primaryAxisOfAttack |
P13659
|
FINISHED |
| Object | south of Kharkiv |
—
|
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: south of Kharkiv | Statement: [Second Battle of Kharkov, primaryAxisOfAttack, south of Kharkiv]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryAxisOfAttack Context triple: [Second Battle of Kharkov, primaryAxisOfAttack, south of Kharkiv]
-
A.
primaryAxisFormation
Indicates the process or relationship by which the main structural or organizational axis of a system, body, or object is established or developed.
-
B.
ridgeAxis
Indicates the central line or crest along the top of a ridge that defines its main axis or direction.
-
C.
primaryAlignment
Indicates the main or most significant way in which one entity is aligned, associated, or in agreement with another entity, standard, or category.
-
D.
primaryDirection
chosen
Indicates the main or dominant directional orientation associated with an entity or relation.
-
E.
usesAxis
Indicates that one entity employs or relies on another entity as a reference axis or basis for orientation, measurement, or organization.
- 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_69ad857bb4c88190a4cf27893fcabed8 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada1e70b9081908c801d084a6ae992 |
completed | March 8, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_69ad9debb6308190be28378ae1fc98af |
completed | March 8, 2026, 4:03 p.m. |
Created at: March 8, 2026, 3:03 p.m.