Triple
T27962631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balurghat subdivision |
E704622
|
entity |
| Predicate | subdivisionOfficerTitle |
P85416
|
FINISHED |
| Object | Sub-Divisional Officer |
—
|
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: Sub-Divisional Officer | Statement: [Balurghat subdivision, subdivisionOfficerTitle, Sub-Divisional Officer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subdivisionOfficerTitle Context triple: [Balurghat subdivision, subdivisionOfficerTitle, Sub-Divisional Officer]
-
A.
notableOfficerTitle
Indicates that an entity holds or is associated with a particularly distinguished or noteworthy officer position or title.
-
B.
typicalOfficeHolderTitle
chosen
Indicates the standard or commonly used title typically held by the office holder of a given position or role.
-
C.
officeHolderTitle
Indicates the official position or title held by a person in an office or role.
-
D.
commissionerTitle
Indicates the official title or designation held by a person serving in the role of commissioner.
-
E.
deputyExecutiveHeadTitle
Indicates the official job title held by a person serving as the deputy to an organization's executive head.
- 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_69ef841061e48190b5570f9562f7434d |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 7:32 p.m.