Triple
T3629099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brunei British protectorate |
E76910
|
entity |
| Predicate | endOfBritishResidentialSystem |
P10272
|
FINISHED |
| Object | 1959 |
—
|
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: 1959 | Statement: [Brunei British protectorate, endOfBritishResidentialSystem, 1959]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endOfBritishResidentialSystem Context triple: [Brunei British protectorate, endOfBritishResidentialSystem, 1959]
-
A.
colonialPeriodEnd
chosen
Indicates the time or event at which a colonial period or colonial rule over a territory comes to an end.
-
B.
viewOnBritishRule
Indicates a person or group's attitude, opinion, or stance toward British colonial rule.
-
C.
ruledEnglandUntil
Indicates that a person or entity exercised sovereign or governing authority over England up to a specified end time.
-
D.
capitalDuringBritishRule
Indicates that a place served as the capital of a region or polity specifically during the period of British rule.
-
E.
royalGovernmentEnd
Indicates the point in time or event at which a royal form of government ceases to exist or loses its governing authority.
- 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_69ad85dc03948190b35b7189e4175bcc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc2df2b708190afef6925a53ec551 |
completed | March 8, 2026, 6:41 p.m. |
| PD | Predicate disambiguation | batch_69adb8410a5881909c94818d7060b2b0 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.