Triple
T3727853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DVB-S |
E78991
|
entity |
| Predicate | multipleAccess |
P51280
|
FINISHED |
| Object | single-carrier per transponder |
—
|
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: single-carrier per transponder | Statement: [DVB-S, multipleAccess, single-carrier per transponder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: multipleAccess Context triple: [DVB-S, multipleAccess, single-carrier per transponder]
-
A.
secondaryAccessMode
Indicates an additional, non-primary way in which an entity can be accessed, used, or interacted with.
-
B.
canOperateInMultiple
Indicates that an entity is capable of functioning or being used across more than one context, environment, or mode.
-
C.
multipleAccessSchemeUplink
Indicates that the uplink communication uses multiple access schemes to allow multiple users or signals to share the same transmission resources.
-
D.
cannotHoldSimultaneously
Indicates that two conditions or states are mutually exclusive and cannot both be true or occur at the same time.
-
E.
supportsMultiuser
Indicates that the subject is capable of handling or enabling simultaneous use by multiple users.
- F. None of above. chosen
Provenance (4 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_69ad8b0e4650819090ad7cef094285e8 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcaf921bc81908bb347d6b9204670 |
completed | March 8, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69adc0452f5081909c79e114a86cce8c |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc226fffc81909c679b44e611fee6 |
completed | March 8, 2026, 6:38 p.m. |
Created at: March 8, 2026, 3:34 p.m.