Triple
T16867225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curzon Line |
E410072
|
entity |
| Predicate | approximateTo |
P4460
|
FINISHED |
| Object | modern Poland–Belarus border |
—
|
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: modern Poland–Belarus border | Statement: [Curzon Line, approximateTo, modern Poland–Belarus border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateTo Context triple: [Curzon Line, approximateTo, modern Poland–Belarus border]
-
A.
approximates
chosen
Indicates that one entity is close to, but not exactly equal to, the value, form, or behavior of another entity.
-
B.
approximationType
Indicates the specific method or scheme used to approximate a value, function, or relationship in a given context.
-
C.
offsetStandardApprox
Indicates that one value serves as an approximate standard or baseline from which another value is offset or deviates.
-
D.
approximateSquare
Indicates that one quantity is approximately equal to the square of another quantity, within some acceptable margin of error.
-
E.
roundOf
Indicates that one event, match, or game occurs as a specific stage or phase within a larger competition or tournament.
- 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b50983148190a116f7e7017ccb1c |
completed | April 18, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69e32b8cbb048190878a259cc5be960e |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:24 a.m.