Triple
T29937357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bavaria |
E760404
|
entity |
| Predicate | hasNeighboringRegionAcrossBorder |
P85348
|
FINISHED |
| Object | Carinthia |
—
|
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: Carinthia | Statement: [Bavaria, hasNeighboringRegionAcrossBorder, Carinthia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNeighboringRegionAcrossBorder Context triple: [Bavaria, hasNeighboringRegionAcrossBorder, Carinthia]
-
A.
hasNeighboringExclave
Indicates that one entity possesses an exclave that directly borders or is adjacent to an exclave of another entity.
-
B.
hasEconomicRegionAlongBorder
Indicates that two entities share a border along which a defined economic region or zone exists or is recognized.
-
C.
hasBorderWithinCountry
Indicates that one region or area shares an internal boundary with another region or area within the same country.
-
D.
hasNeighbouringState
chosen
Indicates that one state shares a common border or is directly adjacent geographically to another state.
-
E.
hasCrossBorderArea
Indicates that an entity is associated with or spans a geographic area that extends across national or jurisdictional borders.
- 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_69f22463f3648190a603c3ff305c660b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fe744faca881908e11e90e0a35653f |
completed | May 8, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69fe734cbf7081909a552c5cf3b5ea59 |
completed | May 8, 2026, 11:35 p.m. |
Created at: April 29, 2026, 6:21 p.m.