Triple
T18538334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PIN code system of India |
E453022
|
entity |
| Predicate | firstDigitRepresents |
P35107
|
FINISHED |
| Object | postal zone |
—
|
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: postal zone | Statement: [PIN code system of India, firstDigitRepresents, postal zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstDigitRepresents Context triple: [PIN code system of India, firstDigitRepresents, postal zone]
-
A.
firstDigitEncoding
chosen
Indicates that one entity encodes or represents the first digit of another entity (such as a number, code, or identifier).
-
B.
firstPartRepresents
Indicates that the initial segment or portion of something stands for, symbolizes, or denotes a larger whole or specific concept.
-
C.
digitSymbolForOne
Indicates that something is the written or symbolic representation used to denote the numeric value one.
-
D.
numericPartRepresents
Indicates that a numeric component of something stands for or encodes a specific value, property, or aspect of that thing.
-
E.
isFirstNumberOneFor
Indicates that the first number in a given pair, sequence, or context is equal to one for the associated entity or situation.
- 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.