Triple
T25331266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chinsurah subdivision |
E635157
|
entity |
| Predicate | subdivisionalHeadquarters |
P155625
|
FINISHED |
| Object | Chinsurah |
—
|
NE NERFINISHED |
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: Chinsurah | Statement: [Chinsurah subdivision, subdivisionalHeadquarters, Chinsurah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subdivisionalHeadquarters Context triple: [Chinsurah subdivision, subdivisionalHeadquarters, Chinsurah]
-
A.
subdivisionHeadquartersOf
chosen
Indicates that a location serves as the main administrative headquarters for a specific subdivision of a larger organization or entity.
-
B.
capitalOfSubdivision
Indicates that a place serves as the administrative capital of a specified subnational division (such as a state, province, or region).
-
C.
districtHeadquartersSince
Indicates the time from which a particular location has served as the administrative headquarters of a specified district.
-
D.
capitalCitySubdivisionOf
Indicates that a capital city is an administrative or territorial subdivision of a larger governing region or entity.
-
E.
districtHeadquartersLocation
Indicates the place where the administrative headquarters of a district is located.
- 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_69e75a9908108190a95427a97020632a |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f5f6baf2d48190a6a4cd6501be87d2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 1:30 p.m.