Triple
T14096610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahra Governorate |
E339267
|
entity |
| Predicate | hasBorderTypeWithArabianSea |
P112811
|
FINISHED |
| Object | maritime border |
—
|
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: maritime border | Statement: [Mahra Governorate, hasBorderTypeWithArabianSea, maritime border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderTypeWithArabianSea Context triple: [Mahra Governorate, hasBorderTypeWithArabianSea, maritime border]
-
A.
hasLandBorderWithSea
Indicates that an entity’s land area directly borders or touches a sea along its coastline.
-
B.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
C.
hasCoastalTaluka
Indicates that an administrative subdivision (taluka) is located along or includes a coastal area.
-
D.
hasBorderWithinCountry
Indicates that one region or area shares an internal boundary with another region or area within the same country.
-
E.
bordersStateAcrossSea
Indicates that one state is separated from another by a sea but still directly borders it across that body of water.
- 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_69d81c69b5c8819094aa1abf18302908 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5fb926288190a7f0f50d1d585d76 |
completed | April 14, 2026, 3:39 p.m. |
| PD | Predicate disambiguation | batch_69de05b2f7e481908a9a7d40153234c0 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de2398856c81908bed6070e4ca6ab1 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:22 p.m.