Triple
T5632196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clermont-Ferrand arrondissement |
E147858
|
entity |
| Predicate | borderingUnitType |
P64694
|
FINISHED |
| Object | other arrondissements of Puy-de-Dôme department |
—
|
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: other arrondissements of Puy-de-Dôme department | Statement: [Clermont-Ferrand arrondissement, borderingUnitType, other arrondissements of Puy-de-Dôme department]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderingUnitType Context triple: [Clermont-Ferrand arrondissement, borderingUnitType, other arrondissements of Puy-de-Dôme department]
-
A.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
B.
countryBorderType
Indicates the type or nature of the border relationship that exists between two countries.
-
C.
provinceBordering
Indicates that two provinces share a common boundary or border with each other.
-
D.
borderRegion
Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
-
E.
borderRegionOf
Indicates that one region lies along, touches, or forms part of the boundary of another 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_69c00907bc8881909ed760d3ed73ef35 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0225e8e848190a9ccd48fc0d74e5c |
completed | March 22, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69c01b1f12ec8190b4b9d9ee31cabe19 |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f0684908190ae2d14f0bd2ab892 |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:40 p.m.