Triple
T13104357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jehanabad |
E310804
|
entity |
| Predicate | hasPINCodeRange |
P476
|
FINISHED |
| Object | 8044xx |
—
|
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: 8044xx | Statement: [Jehanabad, hasPINCodeRange, 8044xx]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPINCodeRange Context triple: [Jehanabad, hasPINCodeRange, 8044xx]
-
A.
hasPINCode
Indicates that an entity is associated with or assigned a specific personal identification number (PIN) code.
-
B.
hasPINCodeSystem
Indicates that an entity is equipped with or uses a PIN code–based authentication or access control system.
-
C.
postalCodeRange
chosen
Indicates that one entity specifies a contiguous range of postal codes applicable to another entity or context.
-
D.
hasPin
Indicates that one entity possesses, includes, or is equipped with a specific pin (such as a connector pin, security PIN, or fastening pin).
-
E.
hasPierNumberRange
Indicates that an entity is associated with a continuous range of pier numbers, from a starting pier number to an ending pier number.
- 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_69d806a872d08190a329806f8ff30df4 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98153255c8190b6ab64ac0c4716f8 |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d98041a3548190a05ddd83dbb660fa |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:05 p.m.