Triple
T11217111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KNIP |
E265466
|
entity |
| Predicate | hasIATACode |
P2569
|
FINISHED |
| Object | NIP |
E265465
|
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: NIP | Statement: [KNIP, hasIATACode, NIP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: NIP Context triple: [KNIP, hasIATACode, NIP]
-
A.
NIP
NIP is the commonly used acronym for the U.S. National Intelligence Program, which funds and coordinates the nation’s primary intelligence activities across multiple agencies.
-
B.
NIP
chosen
NIP is the IATA airport code for Naval Air Station Jacksonville, a major U.S. Navy air base located in Jacksonville, Florida.
-
C.
NIPP
NIPP is a U.S. government framework that guides the protection and resilience of the nation’s critical infrastructure and key resources.
-
D.
NIIP
NIIP is a Russian defense enterprise best known for designing advanced radar and fire-control systems for surface-to-air missile complexes and combat aircraft.
-
E.
NI
NI is the vehicle registration code used on license plates for the German federal state of Lower Saxony.
- 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_69d6aac59460819089b9848b27f57848 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8ea19e8819095d5d02c1f145534 |
completed | April 9, 2026, 5:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e49762e3188190ba3c0e01cf04f6a1 |
completed | April 19, 2026, 8:50 a.m. |
Created at: April 8, 2026, 9:30 p.m.