Triple
T7790187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kasoa |
E187355
|
entity |
| Predicate | regionCapitalDistanceRelation |
P79023
|
FINISHED |
| Object | west of Cape Coast–Accra corridor |
—
|
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: west of Cape Coast–Accra corridor | Statement: [Kasoa, regionCapitalDistanceRelation, west of Cape Coast–Accra corridor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionCapitalDistanceRelation Context triple: [Kasoa, regionCapitalDistanceRelation, west of Cape Coast–Accra corridor]
-
A.
distanceFromCapital
Indicates the measured distance between a given location and the capital city of its corresponding region or country.
-
B.
countryCapitalDistrict
Indicates that a specified district serves as the capital district (administrative capital area) of a given country.
-
C.
prefectureCapitalDistance
Indicates the distance between a prefecture and its designated capital city.
-
D.
countryCapitalRelation
Indicates that one entity is the capital city of the country represented by the other entity.
-
E.
countryCapitalNearby
Indicates that a country’s capital city is geographically close to a specified location or entity.
- 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_69ca82af2d2c8190963861f5e0b8bf21 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cae7ea13f08190a60c5f1863bce816 |
completed | March 30, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69caa488532c819093ac40bba0b3c7ef |
completed | March 30, 2026, 4:27 p.m. |
| PDg | Predicate description generation | batch_69cae7e47c5c8190bca90d45b3cdc25e |
completed | March 30, 2026, 9:15 p.m. |
Created at: March 30, 2026, 4:25 p.m.