Triple
T10551402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Limoges – Bellegarde Airport |
E248954
|
entity |
| Predicate | pushpinLabel |
P9248
|
FINISHED |
| Object | LIG |
E870261
|
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: LIG | Statement: [Limoges – Bellegarde Airport, pushpinLabel, LIG]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LIG Context triple: [Limoges – Bellegarde Airport, pushpinLabel, LIG]
-
A.
LIG
chosen
LIG is the IATA airport code for Limoges – Bellegarde Airport in Limoges, France.
-
B.
Liga
Liga is the Spanish name commonly used to refer to the Catholic League, a powerful alliance of Catholic states formed during the French Wars of Religion to oppose Protestant influence.
-
C.
Ligatne
Ligatne is a small town in Latvia known for its scenic location within the Gauja National Park and its historic paper mill heritage.
-
D.
I liga
I liga is the second-highest tier of professional football in the Polish league system, sitting just below the Ekstraklasa.
-
E.
LGK
LGK is the IATA airport code for Langkawi International Airport, the main air gateway to the Langkawi archipelago in Malaysia.
- 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_69d381c733c08190ab1dd6239f5f34ae |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d526d4c4048190a104d6e088f565b3 |
completed | April 7, 2026, 3:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d94b3148dc81908720c27e58a325ab |
completed | April 10, 2026, 7:10 p.m. |
Created at: April 6, 2026, 12:34 p.m.