Triple
T10826823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osmocom project |
E255516
|
entity |
| Predicate | develops |
P73
|
FINISHED |
| Object | OsmoSGSN |
E255522
|
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: OsmoSGSN | Statement: [Osmocom project, develops, OsmoSGSN]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: OsmoSGSN Context triple: [Osmocom project, develops, OsmoSGSN]
-
A.
osmo-sgsn
chosen
osmo-sgsn is an open-source Serving GPRS Support Node implementation used in mobile networks, developed as part of the Osmocom project.
-
B.
OSN
OSN is the IATA airport code for Osan Air Base, a major United States Air Force installation in South Korea.
-
C.
OSMA
OSMA is the NASA Office of Safety and Mission Assurance, responsible for overseeing safety, reliability, and quality assurance for the agency’s missions and programs.
-
D.
OSO
OSO is the commonly used abbreviation for the Office of SIGINT Operations, a signals intelligence unit within the U.S. National Security Agency.
-
E.
OPSG
OPSG is a U.S. federal grant program that provides funding to state, local, and tribal law enforcement agencies to enhance border security and cooperation along international land and water borders.
- 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_69d734d1c24881909f56d56207cccbef |
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.