Triple
T38018900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imamganj |
E948568
|
entity |
| Predicate | pincodeRegion |
P177458
|
FINISHED |
| Object | Gaya postal division |
—
|
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: Gaya postal division | Statement: [Imamganj, pincodeRegion, Gaya postal division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pincodeRegion Context triple: [Imamganj, pincodeRegion, Gaya postal division]
-
A.
postalRegionOf
Indicates that a given area or zone serves as the designated postal region for another location or address.
-
B.
hasPINCodeArea
chosen
Indicates that an entity is associated with or located within a specific postal (PIN) code area.
-
C.
locationUnionTerritory
Indicates that a location is situated within, or is part of, a specific union territory.
-
D.
postalArea
Indicates that one entity is the postal or ZIP code area associated with the location or address represented by the other entity.
-
E.
gridCodeRegion
Indicates a relationship where a specific grid code is associated with, or designates, a particular geographic or administrative region.
- 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_69f76efc10448190aff5fb566b98f952 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc995dc2481908b3bd4217f8101e7 |
completed | May 6, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:20 p.m.