Triple
T11617871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Klimov VK-1 |
E275555
|
entity |
| Predicate | usedInAircraft |
P10706
|
FINISHED |
| Object | Lim-5 |
E275556
|
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-5 | Statement: [Klimov VK-1, usedInAircraft, Lim-5]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lim-5 Context triple: [Klimov VK-1, usedInAircraft, Lim-5]
-
A.
Lim-5
chosen
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.
-
B.
LIM
LIM is the IATA airport code for Jorge Chávez International Airport, the main international gateway serving Lima, Peru.
-
C.
LC-5
LC-5 is a historic launch complex at Cape Canaveral used for early U.S. crewed spaceflights during the Mercury program.
-
D.
Lim
The Lim is a river in the western Balkans that flows through Montenegro, Serbia, and Bosnia and Herzegovina before joining the Drina.
-
E.
Lim
Lim is a Korean surname borne by numerous notable individuals across fields such as politics, academia, and the arts.
- 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_69d6aaf84b548190ac072e4fb89ae18f |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a047758081908191c1d564409d9a |
completed | April 10, 2026, 7:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ee873ee6888190ab6e87ed0f4ae731 |
completed | April 26, 2026, 9:44 p.m. |
Created at: April 8, 2026, 9:38 p.m.