Triple
T25017548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Czech Republic–Austria border |
E626179
|
entity |
| Predicate | hasLanguageOnNorthernSide |
P164157
|
FINISHED |
| Object | Czech |
—
|
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: Czech | Statement: [Czech Republic–Austria border, hasLanguageOnNorthernSide, Czech]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLanguageOnNorthernSide Context triple: [Czech Republic–Austria border, hasLanguageOnNorthernSide, Czech]
-
A.
hasLanguageOnEasternSide
Indicates that a specified language is used or spoken on the eastern side of a given area, boundary, or region.
-
B.
northernPartKnownAs
Indicates that the northern portion of an entity is referred to by a particular name or designation.
-
C.
northernContinuationOf
Indicates that one entity is a direct geographic or structural continuation of another entity toward the north.
-
D.
northernBranch
Indicates that one entity functions as the northern division, section, or offshoot of another entity.
-
E.
hasLanguageOnSides
Indicates that an object or medium features written or spoken language present on multiple sides or surfaces.
- F. None of above. chosen
Provenance (4 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_69e2ff27755881908490178e83701160 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f643c204508190a43fe0ec5165b01c |
completed | May 2, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f6430975b481909191219ad13ef77e |
completed | May 2, 2026, 6:31 p.m. |
Created at: April 18, 2026, 6:06 a.m.