Triple
T7634411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ljubljana Jože Pučnik Airport |
E172837
|
entity |
| Predicate | IATAcode |
P418
|
FINISHED |
| Object | LJU |
E680510
|
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: LJU | Statement: [Ljubljana Jože Pučnik Airport, IATAcode, LJU]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LJU Context triple: [Ljubljana Jože Pučnik Airport, IATAcode, LJU]
-
A.
LJU
chosen
LJU is the UN/LOCODE designation for Ljubljana Jože Pučnik Airport, the main international airport serving Ljubljana, Slovenia.
-
B.
LJ
LJ is the third-generation model of the Holden Torana, a compact Australian car produced in the early 1970s and known for its performance-oriented variants.
-
C.
LJ
LJ is the nickname of Larry Johnson, a former NBA All-Star forward best known for his time with the Charlotte Hornets and New York Knicks in the 1990s.
-
D.
LJ
LJ is the IATA airline designator used for the South Korean low-cost carrier Jin Air.
-
E.
LJ
LJ is the station code for Ljubljana Railway Station, the main rail hub of Slovenia’s capital city.
- 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_69c69952849881908fdcea7a93bfc307 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6faa72f2881908479049dd8d181a4 |
completed | March 27, 2026, 9:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8a2159cd0819085bfdb8c7694077b |
completed | March 29, 2026, 3:52 a.m. |
Created at: March 27, 2026, 3:57 p.m.