Triple
T1805180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vrindavan |
E40203
|
entity |
| Predicate | timezone |
P109
|
FINISHED |
| Object | IST |
E162749
|
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: IST | Statement: [Vrindavan, timezone, IST]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IST Context triple: [Vrindavan, timezone, IST]
-
A.
IST
IST is the three-letter IATA airport code for Istanbul Airport, the main international gateway serving Istanbul, Turkey.
-
B.
IST
chosen
IST is the time zone used across India, corresponding to UTC+5:30 and commonly referred to as Indian Standard Time.
-
C.
IST
IST is the Graduate School of Information Science and Technology at the University of Tokyo, a leading institution for advanced research and education in information science, computer science, and related fields.
-
D.
IS
IS is the two-letter ISO 3166-1 alpha-2 country code representing Iceland in international standards and systems.
-
E.
IAS
IAS is India’s premier civil service responsible for administrative leadership and implementation of government policies at the central and state levels.
- 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_69a88643a3388190a612f2ebe1fb29e7 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69aa659798b88190bd3070349ce6bebb |
completed | March 6, 2026, 5:26 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69adb5df20948190943a60c209270b62 |
completed | March 8, 2026, 5:46 p.m. |
Created at: March 4, 2026, 7:32 p.m.