Triple
T10827113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | osmo-pcu |
E255521
|
entity |
| Predicate | relatedProject |
P2830
|
FINISHED |
| Object | osmo-bts |
E255520
|
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: osmo-bts | Statement: [osmo-pcu, relatedProject, osmo-bts]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: osmo-bts Context triple: [osmo-pcu, relatedProject, osmo-bts]
-
A.
osmo-bts
chosen
osmo-bts is an open-source software implementation of a GSM base transceiver station, widely used in mobile network research, development, and testing.
-
B.
OsmocomBB
OsmocomBB is an open-source GSM baseband software project that replaces proprietary firmware on mobile phones to enable research, experimentation, and security analysis of cellular networks.
-
C.
osmo-sgsn
osmo-sgsn is an open-source Serving GPRS Support Node implementation used in mobile networks, developed as part of the Osmocom project.
-
D.
osmo-pcu
osmo-pcu is an open-source GSM/GPRS packet control unit software project, best known as part of the Osmocom mobile communications stack initiated by Harald Welte.
-
E.
Osmocom project
The Osmocom project is an open-source initiative focused on developing and reverse-engineering mobile communication infrastructure and protocols, particularly for GSM and related cellular technologies.
- 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_69de8592d8f08190ac577395ad7cc557 |
completed | April 14, 2026, 6:21 p.m. |
Created at: April 8, 2026, 9:19 p.m.