Triple
T16398365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schwenninger Wild Wings |
E398243
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | SWW |
E398243
|
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: SWW | Statement: [Schwenninger Wild Wings, abbreviation, SWW]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SWW Context triple: [Schwenninger Wild Wings, abbreviation, SWW]
-
A.
SWW
chosen
SWW is the common abbreviation for the Schwenninger Wild Wings, a professional ice hockey team based in Schwenningen, Germany.
-
B.
SWU
SWU is the commonly used abbreviation for Southwest University, a comprehensive higher education institution in China.
-
C.
WSSS
WSSS is the ICAO airport code for Singapore Changi Airport, one of the world’s busiest and most highly rated international air hubs.
-
D.
S2W
S2W is a U.S. Navy submarine nuclear reactor plant design used to power early nuclear-powered submarines.
-
E.
SWM
SWM is the municipal utility company of Munich, Germany, responsible for providing services such as energy, water, and public transportation.
- 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_69d87f2950248190bc8ad9b9bebdc8c8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e327cc5c9c8190ba1a70f9e430cefb |
completed | April 18, 2026, 6:42 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a003c5bcc7c81909dc1d3a9a1b7f50a |
completed | May 10, 2026, 8:05 a.m. |
Created at: April 10, 2026, 5:09 a.m.