Triple
T18538335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PIN code system of India |
E453022
|
entity |
| Predicate | secondDigitRepresents |
P132062
|
FINISHED |
| Object | sub-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: sub-zone | Statement: [PIN code system of India, secondDigitRepresents, sub-zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondDigitRepresents Context triple: [PIN code system of India, secondDigitRepresents, sub-zone]
-
A.
secondPartRepresents
Indicates that one part of something serves as the representation, expression, or depiction of a preceding part.
-
B.
secondLetterRepresents
Indicates that the second letter of one entity stands for, symbolizes, or denotes another entity or concept.
-
C.
digitSymbolForTwo
Indicates the written or printed symbol that represents the numerical value two.
-
D.
secondFingerRepresents
Indicates that the second finger is used as a symbolic representation or stand-in for another entity, concept, or value.
-
E.
secondLevelRepresents
Indicates that one entity serves as a secondary or subordinate representation of another, typically refining or detailing the primary representation.
- 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_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. |
| PDg | Predicate description generation | batch_69e46d2b93bc8190a6070018d7046547 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:37 a.m.