Triple
T31671111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arhavi District |
E808270
|
entity |
| Predicate | hasProvinceNeighbor |
P62207
|
FINISHED |
| Object | Rize Province |
—
|
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: Rize Province | Statement: [Arhavi District, hasProvinceNeighbor, Rize Province]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProvinceNeighbor Context triple: [Arhavi District, hasProvinceNeighbor, Rize Province]
-
A.
hasNearbyProvince
Indicates that one province is geographically close to or directly adjacent to another province.
-
B.
adjacentProvince
chosen
Indicates that two provinces share a common boundary and are directly next to each other geographically.
-
C.
hasNeighbouringState
Indicates that one state shares a common border or is directly adjacent geographically to another state.
-
D.
hasNeighboringCityState
Indicates that one city-state is geographically adjacent to or directly borders another city-state.
-
E.
nearProvince
Indicates that one province is geographically close to or bordering another province.
- 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_69f348dbeef4819080b446a7feb6340b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a007aa8d3a481908543f9b5d562a90c |
completed | May 10, 2026, 12:31 p.m. |
| PD | Predicate disambiguation | batch_6a007a44996481908688ccfdbc56511d |
completed | May 10, 2026, 12:29 p.m. |
Created at: April 30, 2026, 11:01 p.m.