Triple
T10560150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | QUIC Loss Detection and Congestion Control |
E249195
|
entity |
| Predicate | aimsTo |
P79
|
FINISHED |
| Object | ensure reliable data transmission on the internet |
—
|
LITERAL FINISHED |
How this triple was built (1 step)
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: ensure reliable data transmission on the internet | Statement: [QUIC Loss Detection and Congestion Control, aimsTo, ensure reliable data transmission on the internet]
Provenance (2 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_69d381c8bd708190acf3d275c908251e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5271f3c6c819080b49fbe3aa09e09 |
completed | April 7, 2026, 3:47 p.m. |
Created at: April 6, 2026, 12:35 p.m.