Triple
T19424891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Sea trade network |
E485955
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | Kaffa |
—
|
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: Kaffa | Statement: [Black Sea trade network, hasPart, Kaffa]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kaffa Context triple: [Black Sea trade network, hasPart, Kaffa]
-
A.
Kafa
Kafa is an Omotic language spoken primarily in southwestern Ethiopia by the Kafa people.
-
B.
Caffa
chosen
Caffa is the historical name of the Crimean port city now known as Feodosia, which was a major Genoese trading colony and a key Black Sea commercial hub in the Middle Ages.
-
C.
Caffee Oromia
Caffee Oromia is the regional parliament of Ethiopia’s Oromia Region, responsible for making laws and overseeing the regional government.
-
D.
Kaffa Zone
Kaffa Zone is an administrative area in southwestern Ethiopia known as the historic homeland of the Kaffa people and as one of the regions associated with the origin of coffee.
-
E.
Sidamo
Sidamo is a Cushitic language spoken primarily in southern Ethiopia by the Sidama people.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63217bd2c81909e216e13aa4c487d |
completed | April 20, 2026, 2:03 p.m. |
Created at: April 10, 2026, 1:37 p.m.