Triple
T31251094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perumbavoor |
E796817
|
entity |
| Predicate | postalDivision |
P171498
|
FINISHED |
| Object | Aluva postal division |
—
|
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: Aluva postal division | Statement: [Perumbavoor, postalDivision, Aluva postal division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postalDivision Context triple: [Perumbavoor, postalDivision, Aluva postal division]
-
A.
postalArea
Indicates that one entity is the postal or ZIP code area associated with the location or address represented by the other entity.
-
B.
postalCounty
Indicates the county associated with an entity for postal addressing or mail delivery purposes.
-
C.
postalRegionOf
Indicates that a given area or zone serves as the designated postal region for another location or address.
-
D.
postalCode
Indicates the numerical or alphanumerical code assigned to a geographic area for mail delivery associated with an entity.
-
E.
postalName
Indicates the standardized name or label used for addressing and postal purposes associated with an entity.
- F. None of above. chosen
Provenance (4 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_69f224dc84d0819081f1cb6f9127e6b1 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69edae2448190925ce701c8792c52 |
completed | May 3, 2026, 1:03 a.m. |
Created at: April 29, 2026, 9:11 p.m.