Triple
T22819178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IS-136 |
E565181
|
entity |
| Predicate | multipleAccessTechnique |
P23649
|
FINISHED |
| Object | time-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: time-division multiple access | Statement: [IS-136, multipleAccessTechnique, time-division multiple access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: multipleAccessTechnique Context triple: [IS-136, multipleAccessTechnique, time-division multiple access]
-
A.
multipleAccess
Indicates that an entity can be accessed or used by more than one agent, user, or process, either simultaneously or sequentially.
-
B.
multipleAccessSchemeUplink
chosen
Indicates that the uplink communication uses multiple access schemes to allow multiple users or signals to share the same transmission resources.
-
C.
primaryAccessTechnologies
Indicates the main technologies or methods used to provide access or connectivity between entities.
-
D.
multipleAccessSchemeDownlink
Indicates that the downlink transmission uses more than one access scheme simultaneously or in combination.
-
E.
allowedTechnique
Indicates that a particular technique or method is permitted or acceptable to use in a given context or under specified rules.
- 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_69e2458426188190b58b8ab4844fe420 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17dce762c8190934fb921f942c9fd |
completed | April 29, 2026, 3:41 a.m. |
| PD | Predicate disambiguation | batch_69eed2d117088190acbfe130d84f8627 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:33 p.m.