Triple
T25017526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Czech Republic–Austria border |
E626179
|
entity |
| Predicate | memberStateBorderOf |
P159714
|
FINISHED |
| Object | European Union |
—
|
NE NERFINISHED |
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: European Union | Statement: [Czech Republic–Austria border, memberStateBorderOf, European Union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberStateBorderOf Context triple: [Czech Republic–Austria border, memberStateBorderOf, European Union]
-
A.
borderStateOf
Indicates that one state shares a common boundary or border with another state.
-
B.
memberStatesShareBorderAlong
Indicates that two member states have a common boundary running along a specified geographic feature or segment.
-
C.
borderingStateOrTerritory
Indicates that one state or territory shares a common boundary with another state or territory.
-
D.
provinceBordering
Indicates that two provinces share a common boundary or border with each other.
-
E.
isBorderMunicipality
Indicates that a municipality is located on or directly adjacent to the border of a larger administrative region, country, or jurisdiction.
- 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_69f5f7a205688190b8f36bff5013247c |
completed | May 2, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 18, 2026, 6:06 a.m.