Triple
T236666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calcutta |
E4838
|
entity |
| Predicate | startTimeAsCapitalOfBritishIndia |
P5604
|
FINISHED |
| Object | 1772 |
—
|
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: 1772 | Statement: [Calcutta, startTimeAsCapitalOfBritishIndia, 1772]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTimeAsCapitalOfBritishIndia Context triple: [Calcutta, startTimeAsCapitalOfBritishIndia, 1772]
-
A.
broughtUnderBritishCrown
Indicates that an entity was placed under the authority, control, or sovereignty of the British Crown.
-
B.
dateReorganizedAsCentralProvincesAndBerar
Indicates the date on which an entity was reorganized into the administrative unit known as the Central Provinces and Berar.
-
C.
inauguratedAsCapital
chosen
Indicates that a place was officially declared and established as the capital of a political or administrative entity.
-
D.
formerColonyEstablishedIn
Indicates that a former colony was originally established in a specified year or time period.
-
E.
wasFirstCapitalOf
Indicates that one place previously served as the earliest or original capital city of another political or administrative entity.
- 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_69a257c3d0708190b0871c4269d273e6 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25ccc5d548190b505bf1d99db41bd |
completed | Feb. 28, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69a25b5dc640819092669575731c393f |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.