Triple
T25447537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nairobi–Karachi |
E637676
|
entity |
| Predicate | servedRegion2 |
P103169
|
FINISHED |
| Object | South Asia |
—
|
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: South Asia | Statement: [Nairobi–Karachi, servedRegion2, South Asia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedRegion2 Context triple: [Nairobi–Karachi, servedRegion2, South Asia]
-
A.
servesRegionAcrossFrom
Indicates that a service or entity operates in a region that is geographically located directly across from another specified region.
-
B.
regionServedByPayload
chosen
Indicates that a specific geographic or administrative region is the area covered or served by a given payload (such as a service, delivery, or data package).
-
C.
regionServedFromHub
Indicates that a particular region receives its services, operations, or logistical support from a specified hub location.
-
D.
issuerRegionServed
Indicates the geographic region or area that the issuer provides services to or operates within.
-
E.
formerServesRegion
Indicates that an entity previously served, represented, or had official responsibility for a given region, but no longer does so.
- 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_69e75db7c5048190b8da9cd7eeedb610 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 21, 2026, 2:02 p.m.