Triple
T7872952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silchar Airport |
E182781
|
entity |
| Predicate | hasCode |
P9567
|
FINISHED |
| Object | VEKU |
E182782
|
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: VEKU | Statement: [Silchar Airport, hasCode, VEKU]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: VEKU Context triple: [Silchar Airport, hasCode, VEKU]
-
A.
VEKU
chosen
VEKU is the ICAO airport code assigned to Silchar Airport in Assam, India.
-
B.
UVEK
UVEK is the German abbreviation for Switzerland’s Federal Department of the Environment, Transport, Energy and Communications, the federal ministry responsible for environmental policy, infrastructure, and related regulatory matters.
-
C.
Vekoma
Vekoma is a Dutch roller coaster and amusement ride manufacturer known worldwide for designing and building a wide range of thrill and family attractions for theme parks.
-
D.
Vé
Vé is a Norse god, one of Odin’s brothers, associated with the creation of the world in Norse mythology.
-
E.
VIKA
VIKA is the ICAO airport code assigned to Kanpur Airport in Uttar Pradesh, India.
- 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_69ca828a17248190b46defe758bc5ad3 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb39a6d93881908d68386e49bea1e3 |
completed | March 31, 2026, 3:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cbdf844f24819091cb8757d29a4a3f |
completed | March 31, 2026, 2:51 p.m. |
Created at: March 30, 2026, 4:56 p.m.