Triple
T2167941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jazan Region |
E46952
|
entity |
| Predicate | hasBorderDirection |
P37328
|
FINISHED |
| Object | south |
—
|
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: south | Statement: [Jazan Region, hasBorderDirection, south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderDirection Context triple: [Jazan Region, hasBorderDirection, south]
-
A.
hasBorderRole
Indicates that an entity holds a specific functional or administrative role related to a border or boundary between regions or jurisdictions.
-
B.
hasBorderConnection
Indicates that two regions or entities share a common boundary or are directly connected along a border.
-
C.
hasBorderTerminus
Indicates that one entity serves as the endpoint or terminal location of another entity’s border or boundary.
-
D.
operatesOnBorderWith
Indicates that one entity conducts activities or exerts influence along or across the shared border it has with another entity.
-
E.
hasBorderLocality
Indicates that one locality is situated along or adjacent to the border of another locality.
- 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_69a88a184cbc8190877791f6552c2484 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc1559ff481908efe3f214b2570dc |
completed | March 7, 2026, 6:10 a.m. |
| PD | Predicate disambiguation | batch_69abbd9efc1c81909a65044a1ffc9038 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abc153b22481908115e5f582c93f12 |
completed | March 7, 2026, 6:10 a.m. |
Created at: March 4, 2026, 7:45 p.m.