Triple
T15471195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tripoli International Airport |
E376662
|
entity |
| Predicate | ICAOcode |
P419
|
FINISHED |
| Object | HLLT |
E376663
|
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: HLLT | Statement: [Tripoli International Airport, ICAOcode, HLLT]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HLLT Context triple: [Tripoli International Airport, ICAOcode, HLLT]
-
A.
HLLT
chosen
HLLT is the ICAO airport code for Tripoli International Airport, the main international gateway serving Tripoli, Libya.
-
B.
HLLS
HLLS is the ICAO airport code for Sabha Airport, a public airport serving the city of Sabha in southwestern Libya.
-
C.
HLLM
HLLM is the ICAO airport code for Mitiga International Airport, a major airport serving Tripoli, Libya.
-
D.
HRLT
HRLT is an acronym commonly used to refer to a Human Rights Liaison Team, typically a specialized group that coordinates and facilitates human rights-related activities within an organization or mission.
-
E.
HLLB
HLLB is the ICAO airport code for Benina International Airport, the main airport serving Benghazi in eastern Libya.
- 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_69d85cd21dcc81908646251b1c26ea00 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f6b49788190b270fdfe92646842 |
completed | April 16, 2026, 1:46 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff2d0543f881909dfbbc77f2a96a1a |
completed | May 9, 2026, 12:48 p.m. |
Created at: April 10, 2026, 3:33 a.m.