Triple
T13442536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orel sector |
E320400
|
entity |
| Predicate | frontSectionOf |
P10176
|
FINISHED |
| Object | German-Soviet front line 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: German-Soviet front line in 1943 | Statement: [Orel sector, frontSectionOf, German-Soviet front line in 1943]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frontSectionOf Context triple: [Orel sector, frontSectionOf, German-Soviet front line in 1943]
-
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.
frontOf
Indicates that one entity is positioned directly before another along a primary viewing or movement direction.
-
C.
frontMaterial
Indicates that one entity is the material that forms the front surface or front-facing part of another entity.
-
D.
frontSector
Indicates that one entity is located in the forward-facing sector or region relative to another entity.
-
E.
partOfFront
chosen
Indicates that one entity constitutes a component or section located at the front portion of another entity.
- 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_69d80761e6cc8190a90c844589998ecc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaee881888190811ddf01bc699864 |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03ce03481908c61094f0cc0c158 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:40 p.m.