Triple
T9725625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stary Sącz |
E235600
|
entity |
| Predicate | hasCarPlatesCode |
P26915
|
FINISHED |
| Object | KNS |
E132096
|
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: KNS | Statement: [Stary Sącz, hasCarPlatesCode, KNS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KNS Context triple: [Stary Sącz, hasCarPlatesCode, KNS]
-
A.
KNS
chosen
KNS is the Polish vehicle registration code assigned to the Nowy Sącz area in the Lesser Poland Voivodeship.
-
B.
KNSE
KNSE is the ICAO airport code for Naval Air Station Whiting Field, a major U.S. Navy aviation training facility in Florida.
-
C.
KSNS
KSNS is the ICAO airport code for Salinas Municipal Airport, a public aviation facility serving Salinas, California.
-
D.
KNA
KNA is the three-letter ISO 3166-1 alpha-3 country code assigned to Saint Kitts and Nevis.
-
E.
KNDS
KNDS is a European defense industry holding company formed as a joint venture between Germany’s Krauss-Maffei Wegmann and France’s Nexter Systems, specializing in military land systems such as tanks and armored vehicles.
- 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_69ca84d0fad481909cdd45aa77416c48 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9e7838448190a7b5b259765a0d95 |
completed | April 1, 2026, 10:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d19fadc2948190b405fb7f249b82aa |
completed | April 4, 2026, 11:33 p.m. |
Created at: March 30, 2026, 8:21 p.m.