Triple
T34871156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cameroon region |
E1005754
|
entity |
| Predicate | borderNegotiationsPeriod |
P200288
|
FINISHED |
| Object | late 19th century |
—
|
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: late 19th century | Statement: [Cameroon region, borderNegotiationsPeriod, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderNegotiationsPeriod Context triple: [Cameroon region, borderNegotiationsPeriod, late 19th century]
-
A.
borderEstablished
Indicates that a formal boundary between two geographic or political entities has been officially defined and put into effect.
-
B.
borderRegime
Indicates the type, rules, or control system governing how movement or interaction is managed across a border between entities.
-
C.
borderTradePointWith
Indicates a location or facility where trade or commercial exchange occurs between two bordering regions or countries.
-
D.
borderOpening
Indicates that a border between two regions is being opened or made accessible for crossing or interaction.
-
E.
borderCultureWith
Indicates that two regions or entities share a common boundary across which cultural traits, practices, or influences are actively exchanged or intertwined.
- 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_69f76dbde1c08190a24e7f9beb564c8d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff7eb7189c81909a8f73fbc4c48e02 |
completed | May 9, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69ff7e54e11081908fb5ce10c5aa7b53 |
completed | May 9, 2026, 6:35 p.m. |
| PDg | Predicate description generation | batch_69ff7eb638c48190aeca7b85b9b698ab |
completed | May 9, 2026, 6:36 p.m. |
Created at: May 3, 2026, 4 p.m.