Triple
T3301774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sporting Kansas City |
E69349
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | SKC |
E69348
|
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: SKC | Statement: [Sporting Kansas City, abbreviation, SKC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SKC Context triple: [Sporting Kansas City, abbreviation, SKC]
-
A.
SKC
chosen
SKC is the commonly used abbreviation for Sporting Kansas City, a professional Major League Soccer club based in Kansas City.
-
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 IATA airline designator used worldwide to identify Scandinavian Airlines on tickets, timetables, and flight information systems.
-
D.
SK
SK is the postcode area covering Stockport and surrounding parts of Greater Manchester and nearby counties in North West England.
-
E.
SKK
SKK was the ISO 4217 currency code for the Slovak koruna, the former official 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_69ad859e529c8190a404273f53cb487d |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0a7d224819080d9a638e08bb8a8 |
completed | March 8, 2026, 5:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b3341e2f508190a21411869375e3e1 |
completed | March 12, 2026, 9:46 p.m. |
Created at: March 8, 2026, 3:11 p.m.