Triple
T30485596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Togo–Ghana border region |
E775709
|
entity |
| Predicate | borderCreatedBy |
P14046
|
FINISHED |
| Object | colonial partition of German Togoland |
—
|
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: colonial partition of German Togoland | Statement: [Togo–Ghana border region, borderCreatedBy, colonial partition of German Togoland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderCreatedBy Context triple: [Togo–Ghana border region, borderCreatedBy, colonial partition of German Togoland]
-
A.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
B.
borderDefinedBy
chosen
Indicates that the boundary or limit of one entity is determined, shaped, or delineated by another entity.
-
C.
borderCountrySide
Indicates that one country shares a land border with the side or region of another country.
-
D.
borderCultureWith
Indicates that two regions or entities share a common boundary across which cultural traits, practices, or influences are actively exchanged or intertwined.
-
E.
borderCharacteristic
Indicates that one entity specifies a property, feature, or quality of the border or boundary of another entity.
- 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_69f22497f91c8190afa7165bc900accd |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe7bfc94bc81909eeec946e8c1c450 |
completed | May 9, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69fe7b74a1188190886f128e07f712da |
completed | May 9, 2026, 12:10 a.m. |
Created at: April 29, 2026, 8:13 p.m.