Triple
T24415128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German–Soviet partition of Poland |
E615563
|
entity |
| Predicate | dividingLine |
P21958
|
FINISHED |
| Object | Curzon Line vicinity |
—
|
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: Curzon Line vicinity | Statement: [German–Soviet partition of Poland, dividingLine, Curzon Line vicinity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dividingLine Context triple: [German–Soviet partition of Poland, dividingLine, Curzon Line vicinity]
-
A.
divisionLine
chosen
Indicates a boundary or separating line that divides one area, group, or portion from another.
-
B.
rulingLine
Indicates that one entity is the ruling or governing lineage, dynasty, or family over another entity (such as a territory, people, or polity).
-
C.
isDividedFrom
Indicates that one entity is separated or partitioned from another, typically by a boundary, barrier, or dividing line.
-
D.
definedLine
Indicates that a specific line (such as a boundary, path, or reference line) has been formally established or specified within a given context.
-
E.
yardLine
Indicates the specific position on a football field, measured in yards from a reference goal line, where a play or event occurs.
- 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_69e2d7e9bfac8190a748952a90957106 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29583c2688190af3bc5d02eb9a3d9 |
completed | April 29, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:12 a.m.