Triple
T6402591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3GPP |
E144097
|
entity |
| Predicate | hasWorkingGroups |
P9939
|
FINISHED |
| Object | TSG RAN |
E23872
|
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: TSG RAN | Statement: [3GPP, hasWorkingGroups, TSG RAN]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TSG RAN Context triple: [3GPP, hasWorkingGroups, TSG RAN]
-
A.
TSG SA
TSG SA is a key 3GPP standards group responsible for overall system architecture and service requirements in mobile telecommunications.
-
B.
TSG CT
TSG CT is a corporate entity associated with TSG SA, likely operating as a related or coordinated business unit within the same organizational group.
-
C.
RAN
chosen
RAN is the 3GPP working group responsible for specifying the radio access network technologies used in mobile communication systems such as LTE and 5G.
-
D.
RAN
The Royal Australian Navy (RAN) is the naval branch of the Australian Defence Force, responsible for conducting maritime military operations and protecting Australia's maritime interests.
-
E.
TSO
TSO is a major Canadian symphony orchestra based in Toronto, renowned for its performances of classical and contemporary orchestral music.
- 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_69c008dc56fc81908d43ffcc11d73bdd |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c068ade8c881908a0472f1de6b7c21 |
completed | March 22, 2026, 10:09 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c638a6e6248190bda7ad3fbd8f4746 |
completed | March 27, 2026, 7:58 a.m. |
Created at: March 22, 2026, 4:35 p.m.