Triple
T3983901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chandannagar |
E86823
|
entity |
| Predicate | mergedWithIndia |
P49624
|
FINISHED |
| Object | 1950s |
—
|
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: 1950s | Statement: [Chandannagar, mergedWithIndia, 1950s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mergedWithIndia Context triple: [Chandannagar, mergedWithIndia, 1950s]
-
A.
accessionToIndia
chosen
Indicates the act or process by which a territory, entity, or region formally joins or is incorporated into India.
-
B.
establishedAsUnionTerritoryOn
Indicates the date or event on which a region was formally designated and constituted as a union territory.
-
C.
wasUnionTerritoryAs
Indicates that an entity held the status of a union territory during a specified time or under specified conditions.
-
D.
wasUnifiedWith
Indicates that two or more previously separate entities were brought together to form a single unified whole.
-
E.
mergedByTreaty
Indicates that two or more entities were combined into a single entity as a result of a formal treaty or agreement.
- 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_69aed93fd9d4819085d3b2137d2346cb |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefa3ef7ac8190abe02f440ff83c43 |
completed | March 9, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69aef8f492ac819089dbb9436dbcdd2b |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:33 p.m.