Triple
T12789091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berar |
E305708
|
entity |
| Predicate | annexedToBritishIndia |
P43098
|
FINISHED |
| Object | early 20th century |
—
|
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: early 20th century | Statement: [Berar, annexedToBritishIndia, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: annexedToBritishIndia Context triple: [Berar, annexedToBritishIndia, early 20th century]
-
A.
integratedIntoIndianUnionAs
Indicates that an entity (such as a region or princely state) was formally incorporated into the political and administrative framework of the Indian Union.
-
B.
replacedByAsCapitalOfBritishIndia
Indicates that one entity ceased to be the capital of British India and was succeeded in that role by another entity.
-
C.
wasAnnexedInPartition
Indicates that a territory or entity was incorporated into another as a result of a formal partition of land or political division.
-
D.
annexedDuring
chosen
Indicates that one entity was formally incorporated into and brought under the control of another entity during a specified time period.
-
E.
annexedInYear
Indicates that one entity was formally annexed or incorporated into another in the specified calendar year.
- 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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e6a61f48190972e241e70bc392c |
completed | April 10, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69d9640ba0688190973e4e7ec8d4a8e0 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:30 p.m.