Triple
T4783600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Capital Territory of Delhi |
E106422
|
entity |
| Predicate | isoCode |
P189
|
FINISHED |
| Object | IN-DL |
E18743
|
NE 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: IN-DL | Statement: [National Capital Territory of Delhi, isoCode, IN-DL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IN-DL Context triple: [National Capital Territory of Delhi, isoCode, IN-DL]
-
A.
IN-DL
chosen
IN-DL is the ISO 3166-2 code representing the National Capital Territory of Delhi in India.
-
B.
IN-DH
IN-DH is the ISO 3166-2 code representing the Indian union territory of Dadra and Nagar Haveli and Daman and Diu.
-
C.
DLS
DLS is a conference that forms part of the SPLASH event, focusing on research and advances in dynamic languages and their applications.
-
D.
DIL
DIL is a German research institute specializing in food technology and innovation.
-
E.
IN-TR
IN-TR is the ISO 3166-2 code that uniquely identifies the Indian state of Tripura.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69bd43f4a9588190bf73e20bc27c03cc |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd65ad3a188190872e47e3a3bf504b |
completed | March 20, 2026, 3:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be43d72e3881909184aeee29b623a0 |
completed | March 21, 2026, 7:08 a.m. |
Created at: March 20, 2026, 1:22 p.m.