Triple
T3381406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurt-Schumacher-Platz |
E71191
|
entity |
| Predicate | hasStationCode |
P1289
|
FINISHED |
| Object | KS |
E116665
|
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: KS | Statement: [Kurt-Schumacher-Platz, hasStationCode, KS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KS Context triple: [Kurt-Schumacher-Platz, hasStationCode, KS]
-
A.
KS
chosen
KS is the standard two-letter postal abbreviation for the U.S. state of Kansas.
-
B.
SK
SK is the vehicle registration code used on license plates for vehicles registered in Skopje, the capital city of North Macedonia.
-
C.
SK
SK is the postcode area covering Stockport and surrounding parts of Greater Manchester and nearby counties in North West England.
-
D.
SK
SK is the IATA airline designator used worldwide to identify Scandinavian Airlines on tickets, timetables, and flight information systems.
-
E.
Sk
Sk is the currency symbol that was used to denote the Slovak koruna, the former national currency of Slovakia before adoption of the euro.
- 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_69ad85a8fd9c819095ecedf838d2bf1b |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb5e9af608190bfb228ef99a87bb7 |
completed | March 8, 2026, 5:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b3344f9b448190aab1038ead60fa48 |
completed | March 12, 2026, 9:46 p.m. |
Created at: March 8, 2026, 3:14 p.m.