Triple
T5479811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 5G NR |
E123441
|
entity |
| Predicate | usesMultipleAccess |
P51280
|
FINISHED |
| Object | OFDMA |
—
|
LITERAL 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: OFDMA | Statement: [5G NR, usesMultipleAccess, OFDMA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMultipleAccess Context triple: [5G NR, usesMultipleAccess, OFDMA]
-
A.
multipleAccess
chosen
Indicates that an entity can be accessed or used by more than one agent, user, or process, either simultaneously or sequentially.
-
B.
canOperateInMultiple
Indicates that an entity is capable of functioning or being used across more than one context, environment, or mode.
-
C.
hasHumanAccess
Indicates that a human is able to access, use, or interact with the referenced entity or resource.
-
D.
typeOfAccess
Indicates the specific kind or level of access that one entity has to another (such as read, write, or execute permissions).
-
E.
controlsAccessTo
Indicates that one entity regulates, manages, or determines the ability of another entity to reach, use, or interact with a resource, location, or service.
- F. None of above.
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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd9248ca348190aa116cace0f9b07a |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd91a58c448190904964a439045e05 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:09 p.m.