Triple
T10827032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | osmo-bts |
E255520
|
entity |
| Predicate | supportsTechnology |
P5090
|
FINISHED |
| Object | GSM |
E123436
|
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: GSM | Statement: [osmo-bts, supportsTechnology, GSM]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: GSM Context triple: [osmo-bts, supportsTechnology, GSM]
-
A.
GSM
chosen
GSM is a second-generation (2G) digital mobile communication standard that became the global foundation for cellular voice and basic data services.
-
B.
GSM
GSM is the common abbreviation for Great St Mary’s Church, the historic University Church located in the center of Cambridge, England.
-
C.
GSM
GSM is the three-letter IATA airport code assigned to Qeshm International Airport in Iran.
-
D.
GPRS
GPRS (General Packet Radio Service) is a mobile data standard that enables packet-switched internet and multimedia services over 2G and 3G cellular networks.
-
E.
GSM-R
GSM-R is a digital radio communication system used across European railways to provide secure voice and data links between trains and railway control centers.
- 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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d734d2b9f88190b79a7b168d7836c8 |
completed | April 9, 2026, 5:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69dff7c45f288190a5235b5d7000a32c |
completed | April 15, 2026, 8:40 p.m. |
Created at: April 8, 2026, 9:19 p.m.