Triple
T4074686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SPJC |
E86733
|
entity |
| Predicate | associatedWithCityCode |
P6089
|
FINISHED |
| Object | LIM |
E86732
|
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: LIM | Statement: [SPJC, associatedWithCityCode, LIM]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LIM Context triple: [SPJC, associatedWithCityCode, LIM]
-
A.
LIM
chosen
LIM is the IATA airport code for Jorge Chávez International Airport, the main international gateway serving Lima, Peru.
-
B.
LIMF
LIMF is the ICAO airport code for Turin Airport, an international airport serving the city of Turin in northern Italy.
-
C.
LIMC
LIMC is the ICAO airport code for Milan Malpensa Airport, a major international airport serving the Milan metropolitan area in Italy.
-
D.
Lim
Lim is a Korean surname borne by numerous notable individuals across fields such as politics, academia, and the arts.
-
E.
Lim-5
The Lim-5 is a Polish-built version of the Soviet MiG-17 jet fighter, produced under license and used primarily by the Polish Air Force during the Cold War.
- 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_69aed93ebe448190a1f1686e28740ac9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefc25e2e08190b3c048e1b8f85bbf |
completed | March 9, 2026, 4:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b56b5c2c948190a2548e26be3eedfd |
completed | March 14, 2026, 2:06 p.m. |
Created at: March 9, 2026, 3:39 p.m.