Triple
T12789106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berar |
E305708
|
entity |
| Predicate | largelyBecamePartOf |
P13314
|
FINISHED |
| Object | Maharashtra in 1960 |
—
|
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: Maharashtra in 1960 | Statement: [Berar, largelyBecamePartOf, Maharashtra in 1960]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: largelyBecamePartOf Context triple: [Berar, largelyBecamePartOf, Maharashtra in 1960]
-
A.
historicallyPartOf
Indicates that one entity was formerly a component, region, or subdivision of another entity during a past historical period, but is not necessarily part of it in the present.
-
B.
laterIncorporatedInto
chosen
Indicates that one entity was subsequently merged into, absorbed by, or formally made part of another entity at a later time.
-
C.
after1945BecamePartOf
Indicates that one entity became a territorial or administrative part of another entity after the year 1945.
-
D.
southernPartBecame
Indicates that the southern portion of an original entity transformed into, or was reconstituted as, another distinct entity.
-
E.
usedToBePartOf
Indicates that an entity was formerly a component or member of another entity but is no longer part of it.
- 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.