Triple
T25017549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Czech Republic–Austria border |
E626179
|
entity |
| Predicate | hasLanguageOnSouthernSide |
P164773
|
FINISHED |
| Object | German |
—
|
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 | Statement: [Czech Republic–Austria border, hasLanguageOnSouthernSide, German]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLanguageOnSouthernSide Context triple: [Czech Republic–Austria border, hasLanguageOnSouthernSide, German]
-
A.
hasLanguageOnNorthernSide
Indicates that a particular language is used or present on the northern side of a specified boundary, area, or object.
-
B.
hasLanguageOnEasternSide
Indicates that a specified language is used or spoken on the eastern side of a given area, boundary, or region.
-
C.
isOnSouthernPartOf
Indicates that one entity is located on the southern part or southern region of another entity.
-
D.
hasSouthBorder
Indicates that one entity shares its southern boundary or border with another entity.
-
E.
hasHistoricalRegionOnSouthernBoundary
Indicates that an entity’s southern boundary is adjacent to or defined by a specific historical region.
- 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_69f650fc44e48190bc0e0a935eac62a6 |
completed | May 2, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f650c466b881908954e43bfebae8a4 |
completed | May 2, 2026, 7:30 p.m. |
Created at: April 18, 2026, 6:06 a.m.