Triple
T23363075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3GPP TSG SA Working Group 3 Security |
E593237
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | SA3 |
—
|
NE NERFINISHED |
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: SA3 | Statement: [3GPP TSG SA Working Group 3 Security, shortName, SA3]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SA3 Context triple: [3GPP TSG SA Working Group 3 Security, shortName, SA3]
-
A.
SA3
chosen
SA3 is the 3GPP security working group responsible for specifying and evolving security architecture and mechanisms across mobile communication standards.
-
B.
SA4
SA4 is a 3GPP working group responsible for the standardization of multimedia codecs, systems, and services in mobile communications.
-
C.
SA2
SA2 is a 3GPP working group responsible for defining the overall system architecture and functional specifications of mobile communication networks.
-
D.
SA5
SA5 is the 3GPP Service and System Aspects working group responsible for management, orchestration, and operations of mobile communication networks.
-
E.
SA6
SA6 is a 3GPP working group responsible for standardizing mission-critical and application-layer services in mobile communication systems.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e25d2593c88190bcdf4a716a94ccb2 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a0aa0ed88190b0198cbfd1bcc59b |
completed | April 29, 2026, 6:09 a.m. |
Created at: April 17, 2026, 5:30 p.m.