Triple
T1701119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Global Telecommunication System |
E36768
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | GTS |
E36768
|
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: GTS | Statement: [Global Telecommunication System, abbreviation, GTS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: GTS Context triple: [Global Telecommunication System, abbreviation, GTS]
-
A.
GTS
GTS is a high-performance, sport-oriented variant of the Holden Monaro produced by Holden’s performance division.
-
B.
GTS
chosen
GTS is an abbreviation commonly used for the Global Telecommunication System, an international network for exchanging meteorological data.
-
C.
GCTS
GCTS is the ICAO airport code for Tenerife South Airport, a major international airport on the island of Tenerife in Spain’s Canary Islands.
-
D.
GTC
GTC is a Polish vehicle registration code assigned to a specific county within the Pomeranian Voivodeship.
-
E.
GSP
GSP is a regional vehicle registration code used on license plates issued in the Pomeranian Voivodeship of Poland.
- 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_69a886163dec8190859c514232a37a05 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa62d6c7c88190998ce97d65395280 |
completed | March 6, 2026, 5:15 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad799f98e48190b9eaf6f5151f4c80 |
completed | March 8, 2026, 1:29 p.m. |
Created at: March 4, 2026, 7:30 p.m.