Triple
T447851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burma (until 1937) |
E7059
|
entity |
| Predicate | incorporationIntoBritishIndia |
P9430
|
FINISHED |
| Object | 1886 |
—
|
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: 1886 | Statement: [Burma (until 1937), incorporationIntoBritishIndia, 1886]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: incorporationIntoBritishIndia Context triple: [Burma (until 1937), incorporationIntoBritishIndia, 1886]
-
A.
replacedByAsCapitalOfBritishIndia
Indicates that one entity ceased to be the capital of British India and was succeeded in that role by another entity.
-
B.
endTimeAsCapitalOfBritishIndia
Indicates the point in time when a location ceased to serve as the capital of British India.
-
C.
broughtUnderBritishCrown
Indicates that an entity was placed under the authority, control, or sovereignty of the British Crown.
-
D.
annexedInYear
chosen
Indicates that one entity was formally annexed or incorporated into another in the specified calendar year.
-
E.
dateReorganizedAsCentralProvincesAndBerar
Indicates the date on which an entity was reorganized into the administrative unit known as the Central Provinces and Berar.
- 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_69a2e7e4676c81909ea0dbdecac0687c |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ef6429e881908aa758da64299a16 |
completed | Feb. 28, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69a2ede1a1108190a4a06b3416ae6156 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.