Triple
T8690086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British North Borneo |
E206263
|
entity |
| Predicate | protectorateProclaimedYear |
P84212
|
FINISHED |
| Object | 1888 |
—
|
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: 1888 | Statement: [British North Borneo, protectorateProclaimedYear, 1888]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protectorateProclaimedYear Context triple: [British North Borneo, protectorateProclaimedYear, 1888]
-
A.
protectorateEstablishedBy
Indicates that a protectorate relationship was formally created or instituted by a particular actor or authority.
-
B.
wasProtectorateOf
Indicates that one entity was formerly under the protection and partial control of another, typically more powerful, entity.
-
C.
annexedInYear
Indicates that one entity was formally annexed or incorporated into another in the specified calendar year.
-
D.
dateOfSovereigntyTransfer
Indicates the date on which sovereignty or governing authority over an entity was formally transferred from one party to another.
-
E.
annexationDate
Indicates the date on which one entity formally annexed or incorporated another entity into its territory or jurisdiction.
- 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_69ca835481fc819084e33d3bc883bfa6 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5734602c81909a0687e00f4a4a26 |
completed | March 31, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69cc4569f9048190b9c86b4c81103d35 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc483f06f48190879f4702c8b4ed00 |
completed | March 31, 2026, 10:18 p.m. |
Created at: March 30, 2026, 6:33 p.m.