Triple
T22688208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Licensed Assisted Access |
E560975
|
entity |
| Predicate | isDownlinkFocused |
P149255
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Licensed Assisted Access, isDownlinkFocused, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDownlinkFocused Context triple: [Licensed Assisted Access, isDownlinkFocused, true]
-
A.
downlinkMethod
Indicates the method or technology used to transmit data from a remote system (e.g., satellite or spacecraft) down to a receiving station.
-
B.
hasDigitalFocus
Indicates that an entity is primarily oriented toward or centered on digital technologies, channels, or activities.
-
C.
multipleAccessSchemeDownlink
Indicates that the downlink transmission uses more than one access scheme simultaneously or in combination.
-
D.
hasSecondaryFocus
Indicates that an entity has an additional, subordinate area of attention, concern, or specialization beyond its primary focus.
-
E.
hasCharacterFocus
Indicates that a work, scene, or segment centers primarily on a particular character’s experiences, perspective, or development.
- 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_69e2454d71b48190a1f80af9f82b6fcf |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f178983fc8819080aa00e45ff77952 |
completed | April 29, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69ee62b2259c819091ed1387a748b9f3 |
completed | April 26, 2026, 7:08 p.m. |
| PDg | Predicate description generation | batch_69ee8843d3308190b6e22bb98ae5c3d8 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:13 p.m.