Triple
T255989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Kursk |
E5437
|
entity |
| Predicate | frontWidth |
P619
|
FINISHED |
| Object | approximately 250 kilometers |
—
|
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: approximately 250 kilometers | Statement: [Battle of Kursk, frontWidth, approximately 250 kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frontWidth Context triple: [Battle of Kursk, frontWidth, approximately 250 kilometers]
-
A.
frontType
Indicates the type or category of a front (e.g., boundary or leading side) that one entity presents or forms relative to another.
-
B.
front
Indicates that one entity is located directly before or facing another entity along a primary viewing or movement direction.
-
C.
hasFront
Indicates that an entity possesses or is associated with a front-facing side, surface, or portion.
-
D.
width
chosen
Indicates the measurement of how wide an entity is, typically the extent of its horizontal dimension from side to side.
-
E.
frontLine
Indicates that an entity is positioned at or associated with the foremost or primary line of engagement, activity, or defense relative to others.
- 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_69a2580a64ac8190ad76e34bb0715b5e |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25d5669008190978bbd7308be11f7 |
completed | Feb. 28, 2026, 3:13 a.m. |
| PD | Predicate disambiguation | batch_69a25b694c08819085bb4b256fa7736f |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:55 a.m.