Triple
T31784625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Leonese |
E811293
|
entity |
| Predicate | geographicallyBorders |
P181353
|
FINISHED |
| Object | Asturian-speaking areas to the north |
—
|
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: Asturian-speaking areas to the north | Statement: [Eastern Leonese, geographicallyBorders, Asturian-speaking areas to the north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geographicallyBorders Context triple: [Eastern Leonese, geographicallyBorders, Asturian-speaking areas to the north]
-
A.
countryBordering
Indicates that one country shares a land or maritime boundary directly with another country.
-
B.
borderingCountryOfState
Indicates that one country shares a land or maritime boundary directly with the specified state.
-
C.
provinceBordering
Indicates that two provinces share a common boundary or border with each other.
-
D.
countryBorderRelation
Indicates that two countries share a common land or maritime boundary with each other.
-
E.
borderingCountryOfRegion
Indicates that a country shares a land or maritime border with a specified geographic 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_69f348e544a48190ab6e700b05f6438c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
| PDg | Predicate description generation | batch_69f7688cea58819098bdfd7c80df7634 |
completed | May 3, 2026, 3:23 p.m. |
Created at: April 30, 2026, 11:37 p.m.