Triple
T18538342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PIN code system of India |
E453022
|
entity |
| Predicate | lowestPossiblePIN |
P26954
|
FINISHED |
| Object | 110001 |
—
|
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: 110001 | Statement: [PIN code system of India, lowestPossiblePIN, 110001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lowestPossiblePIN Context triple: [PIN code system of India, lowestPossiblePIN, 110001]
-
A.
minimumNumber
chosen
Indicates that the associated value is the smallest or least quantity allowed, required, or observed within a given set or context.
-
B.
minimumDenomination
Indicates that one entity specifies the smallest allowable unit or value (minimum denomination) in which another entity can be expressed, transacted, or divided.
-
C.
lowestScore
Indicates that the associated value is the smallest (minimum) score among a set of scores.
-
D.
lowestPoint
Indicates that one entity is the point with the minimum vertical position or value relative to another entity or within a specified context.
-
E.
lowestRank
Indicates that the subject has the least or worst rank in an ordered set compared to all other related entities.
- 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.