Triple
T34871154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cameroon region |
E1005754
|
entity |
| Predicate | borderNegotiationsWith |
P67780
|
FINISHED |
| Object | British Nigeria |
—
|
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: British Nigeria | Statement: [Cameroon region, borderNegotiationsWith, British Nigeria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderNegotiationsWith Context triple: [Cameroon region, borderNegotiationsWith, British Nigeria]
-
A.
borderDisputesWith
Indicates that there are contested or unresolved boundary claims between two entities.
-
B.
borderingRepublic
Indicates that one republic shares a land or maritime border with another republic.
-
C.
borderCultureWith
Indicates that two regions or entities share a common boundary across which cultural traits, practices, or influences are actively exchanged or intertwined.
-
D.
borderingCountryInteraction
Indicates interactions, relationships, or exchanges that occur specifically between countries that share a common border.
-
E.
borderDemarcationTreaties
chosen
Indicates the existence of formal treaties that define, establish, or adjust the official boundary lines between two or more territories or jurisdictions.
- 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_69f76dbde1c08190a24e7f9beb564c8d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff7dcedab08190a719a707d03306e2 |
completed | May 9, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69ff7d0119348190ad462554e81190fe |
completed | May 9, 2026, 6:29 p.m. |
Created at: May 3, 2026, 4 p.m.