Triple
T5481145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TSG SA |
E123468
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | TSG SA |
E123468
|
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: TSG SA | Statement: [TSG SA, abbreviation, TSG SA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TSG SA Context triple: [TSG SA, abbreviation, TSG SA]
-
A.
TSG SA
chosen
TSG SA is a key 3GPP standards group responsible for overall system architecture and service requirements in mobile telecommunications.
-
B.
SZG
SZG is the three-letter IATA airport code for Salzburg Airport in Salzburg, Austria.
-
C.
SGS
SGS is the three-letter ISO 3166-1 alpha-3 country code corresponding to South Georgia and the South Sandwich Islands.
-
D.
SZS
SZS is the ICAO airline designator assigned to SAS Ireland, a subsidiary carrier operating flights on behalf of Scandinavian Airlines.
-
E.
TSO
TSO (The Stationery Office) is a major UK publishing and information services company known for producing and distributing official government and public sector documents.
- 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd924a2eb08190b759b23a6eab5e0a |
completed | March 20, 2026, 6:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf48a2880c8190ad76cf8c3862aede |
completed | March 22, 2026, 1:40 a.m. |
Created at: March 20, 2026, 2:09 p.m.