Triple
T311028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | QUIC |
E7606
|
entity |
| Predicate | IANAProtocolNumber |
P3682
|
FINISHED |
| Object | UDP-based; no separate IP protocol number |
—
|
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: UDP-based; no separate IP protocol number | Statement: [QUIC, IANAProtocolNumber, UDP-based; no separate IP protocol number]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IANAProtocolNumber Context triple: [QUIC, IANAProtocolNumber, UDP-based; no separate IP protocol number]
-
A.
protocolNumber
chosen
Indicates the specific identifying number assigned to a protocol that governs or documents an interaction, process, or agreement between entities.
-
B.
protocolFamily
Indicates that one protocol belongs to, or is categorized under, a broader protocol family or group.
-
C.
transportProtocol
Indicates the communication protocol used to transport data between entities in a networked interaction.
-
D.
portNumber
Indicates the specific communication port assigned to a network connection, service, or endpoint.
-
E.
hasProtocol
Indicates that an entity uses, follows, or is governed by a specified protocol or set of procedural rules.
- 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_69a2e7e7af7881908890039d6be4e9b8 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ea49636c8190a69cbd951fc0a4db |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e940b9e8819092b821ff17ed026b |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:07 p.m.