Triple
T8690085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British North Borneo |
E206263
|
entity |
| Predicate | charterGrantedYear |
P8990
|
FINISHED |
| Object | 1881 |
—
|
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: 1881 | Statement: [British North Borneo, charterGrantedYear, 1881]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: charterGrantedYear Context triple: [British North Borneo, charterGrantedYear, 1881]
-
A.
charterAdoptedIn
Indicates that a charter was formally adopted or enacted at a specific time or in a specific place.
-
B.
charterDate
chosen
Indicates the date on which an organization, institution, or entity was formally established or granted its charter.
-
C.
grantedCharter
Indicates that an authority formally issued an official charter or authorization to an entity.
-
D.
yearOfPromulgation
Indicates the specific year in which something, typically a law or formal decree, was officially enacted or put into effect.
-
E.
introducedLegalCharter
Indicates that an entity formally established or brought into effect a legal charter governing another entity or domain.
- 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_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. |
Created at: March 30, 2026, 6:33 p.m.