Triple
T21191976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TD-SCDMA |
E522232
|
entity |
| Predicate | usesMultipleAccessScheme |
P114887
|
FINISHED |
| Object | code division multiple access |
—
|
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: code division multiple access | Statement: [TD-SCDMA, usesMultipleAccessScheme, code division multiple access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMultipleAccessScheme Context triple: [TD-SCDMA, usesMultipleAccessScheme, code division multiple access]
-
A.
multipleAccessSchemeUplink
Indicates that the uplink communication uses multiple access schemes to allow multiple users or signals to share the same transmission resources.
-
B.
multipleAccess
Indicates that an entity can be accessed or used by more than one agent, user, or process, either simultaneously or sequentially.
-
C.
usesScheme
chosen
Indicates that one entity employs, follows, or is based on a particular scheme, method, or structured plan associated with another entity.
-
D.
canOperateInMultiple
Indicates that an entity is capable of functioning or being used across more than one context, environment, or mode.
-
E.
canOperateInMultipleWith
Indicates that an entity is capable of functioning or being used concurrently within multiple instances, contexts, or configurations of another entity.
- 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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e733381f288190b3da795f62a39568 |
completed | April 21, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f6027c248190a170a36612bd337e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:07 p.m.