Triple
T5770948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HSDPA |
E127328
|
entity |
| Predicate | TTI |
P5680
|
FINISHED |
| Object | 2 ms |
—
|
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: 2 ms | Statement: [HSDPA, TTI, 2 ms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: TTI Context triple: [HSDPA, TTI, 2 ms]
-
A.
Typer
Indicates that one entity serves as the type or classification for another entity.
-
B.
transmission
Indicates the transfer or conveyance of something (such as information, energy, or material) from one entity to another.
-
C.
via
chosen
Indicates that something occurs, is achieved, or is connected by means of, through the use of, or along the route of another entity or medium.
-
D.
tickerFor
Indicates that one entity is the stock ticker symbol used to uniquely identify another entity (typically a publicly traded company or security) in financial markets.
-
E.
terminus
Indicates that one entity serves as the final endpoint or stopping place for another entity’s movement, route, or process.
- 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.