Triple
T34871151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cameroon region |
E1005754
|
entity |
| Predicate | protectorateEstablishedOn |
P182086
|
FINISHED |
| Object | 1884-07-14 |
—
|
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: 1884-07-14 | Statement: [Cameroon region, protectorateEstablishedOn, 1884-07-14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protectorateEstablishedOn Context triple: [Cameroon region, protectorateEstablishedOn, 1884-07-14]
-
A.
protectorateProclaimedYear
Indicates the year in which a protectorate status was officially declared over an entity.
-
B.
protectorateEstablishedBy
Indicates that a protectorate relationship was formally created or instituted by a particular actor or authority.
-
C.
annexationDate
Indicates the date on which one entity formally annexed or incorporated another entity into its territory or jurisdiction.
-
D.
annexedInYear
Indicates that one entity was formally annexed or incorporated into another in the specified calendar year.
-
E.
dateOfSovereigntyTransfer
Indicates the date on which sovereignty or governing authority over an entity was formally transferred from one party to another.
- 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_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f7870dfe108190996c0c68630edc7f |
completed | May 3, 2026, 5:34 p.m. |
Created at: May 3, 2026, 4 p.m.