Triple
T5770938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HSDPA |
E127328
|
entity |
| Predicate | downlinkDirection |
P9929
|
FINISHED |
| Object | network-to-user |
—
|
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: network-to-user | Statement: [HSDPA, downlinkDirection, network-to-user]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: downlinkDirection Context triple: [HSDPA, downlinkDirection, network-to-user]
-
A.
down
Indicates that one entity is located at a lower position or level relative to another entity or reference point.
-
B.
downstreamFrom
Indicates that one entity is located or occurs at a point further along the natural flow or direction of another entity, typically in a linear or directional system such as a river, pipeline, or process sequence.
-
C.
lowerDeckDirection
Indicates the direction or orientation associated with movement or positioning on the lower deck of a structure or vehicle.
-
D.
lapDirection
Indicates the direction or orientation in which a lapping or overlapping action occurs between entities.
-
E.
dataFlowDirection
chosen
Indicates the direction in which data moves or is transmitted from a source entity to a target 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_69c00834f6308190851b0abeddd8ed7e |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02acb12c081908e4beee4a957f9f9 |
completed | March 22, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69c021ce8d3c81909b332cb1c33a61ad |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:50 p.m.