Triple
T18538341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PIN code system of India |
E453022
|
entity |
| Predicate | functionalZoneCode |
P58492
|
FINISHED |
| Object | 9 |
—
|
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: 9 | Statement: [PIN code system of India, functionalZoneCode, 9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionalZoneCode Context triple: [PIN code system of India, functionalZoneCode, 9]
-
A.
zoneCode
chosen
Indicates that an entity is associated with, or assigned to, a specific geographic or administrative zone identified by a code.
-
B.
coreZoneArea
Indicates the area or spatial extent of a designated core zone within a larger region or system.
-
C.
districtCode
Indicates that an entity is associated with, or identified by, a specific administrative district code.
-
D.
locationCode
Indicates the specific coded location associated with an entity, event, or relationship.
-
E.
zoneNumberRange
Indicates that there is an associated range of zone numbers, typically specifying the minimum and maximum zone identifiers applicable in a given context.
- 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_69d8d387b5548190aa030dad2cb4947e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e534030bd88190b25b95305a12a0c1 |
completed | April 19, 2026, 7:58 p.m. |
| PD | Predicate disambiguation | batch_69e469e0025c81908f16ed4f922674af |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:37 a.m.