Triple
T7302405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nabadwip |
E167888
|
entity |
| Predicate | pinCodeCountrySystem |
P7766
|
FINISHED |
| Object | India PIN code system |
—
|
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: India PIN code system | Statement: [Nabadwip, pinCodeCountrySystem, India PIN code system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pinCodeCountrySystem Context triple: [Nabadwip, pinCodeCountrySystem, India PIN code system]
-
A.
postalCodeSystem
chosen
Indicates a system that assigns structured postal codes to geographic areas for organizing and routing mail.
-
B.
postalCodeInCountry
Indicates that a given postal code is assigned to and valid within a particular country.
-
C.
UICCountryCode
Indicates that an entity is associated with a specific country identified by its UIC (International Union of Railways) country code.
-
D.
countryCodePart
Indicates that one entity is a segment or component of a standardized country code associated with another entity.
-
E.
hasPINCode
Indicates that an entity is associated with or assigned a specific personal identification number (PIN) code.
- 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_69c6888c820881909fc68f689fe1c251 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6ebb2261c8190ae9095c8e110b528 |
completed | March 27, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69c6e76e67d88190bd3ca6864f45845a |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:01 p.m.