Triple
T15527943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LEVD |
E369131
|
entity |
| Predicate | hasIATAcode |
P2569
|
FINISHED |
| Object | VLL |
E369130
|
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: VLL | Statement: [LEVD, hasIATAcode, VLL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: VLL Context triple: [LEVD, hasIATAcode, VLL]
-
A.
VLL
chosen
VLL is the three-letter IATA airport code for Valladolid Airport in Spain.
-
B.
VLLB
VLLB is the ICAO airport code for Luang Prabang International Airport in Laos, which serves the historic city of Luang Prabang.
-
C.
VLH
VLH is the commonly used abbreviation for Växjö Lakers HC, a professional ice hockey club based in Växjö, Sweden.
-
D.
VRR
VRR is a geologically distinct, hematite-rich ridge on Mars explored by NASA’s Curiosity rover as a key site for studying the planet’s past environmental conditions.
-
E.
VRR
VRR is the public transport association that coordinates and manages the integrated ticketing and fare system for much of the Rhine-Ruhr metropolitan region in Germany.
- 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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0414620588190958ffde651ccab5f |
completed | April 16, 2026, 1:54 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff45549e4881908ab0769e49ba5dc4 |
completed | May 9, 2026, 2:31 p.m. |
Created at: April 10, 2026, 4:05 a.m.