Triple
T18538360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PIN code system of India |
E453022
|
entity |
| Predicate | languageOfNumerals |
P86768
|
FINISHED |
| Object | Arabic numerals |
—
|
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: Arabic numerals | Statement: [PIN code system of India, languageOfNumerals, Arabic numerals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfNumerals Context triple: [PIN code system of India, languageOfNumerals, Arabic numerals]
-
A.
usesNumeralsFrom
chosen
Indicates that one writing system, notation, or representation employs the numeral symbols originating from another system.
-
B.
expressedInText
Indicates that a particular idea, statement, or piece of information is explicitly conveyed within a given text.
-
C.
definitionInWords
Indicates that one entity provides a verbal or textual explanation or meaning for another entity.
-
D.
spellsOut
Indicates that one entity explicitly writes, states, or presents another entity in full detail, often by expanding an abbreviation, code, or symbolic form into its complete representation.
-
E.
RomanNumeral
Indicates that something is represented or written using the Roman numeral system.
- 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.