Triple
T4402438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G.711 |
E93646
|
entity |
| Predicate | packetizationTypical |
P9638
|
FINISHED |
| Object | 20 ms in VoIP implementations |
—
|
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: 20 ms in VoIP implementations | Statement: [G.711, packetizationTypical, 20 ms in VoIP implementations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: packetizationTypical Context triple: [G.711, packetizationTypical, 20 ms in VoIP implementations]
-
A.
packetSize
Indicates the size or amount of data contained in a packet within a communication or data transfer context.
-
B.
payloadType
Indicates the kind or category of payload associated with or carried by an entity or action.
-
C.
packetDirection
Indicates the direction in which a data packet is traveling between network endpoints (e.g., inbound or outbound).
-
D.
transmissionPattern
Indicates how something is passed or spread from one entity to another, such as the mode or route of transmission.
-
E.
typicalSegmentType
chosen
Indicates that something is classified as belonging to a usual or characteristic type of segment within a broader structure or sequence.
- 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_69b345158c748190a2c040fce2da9980 |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b352d08a0c8190ac6c125df40eca75 |
completed | March 12, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69b34f597998819092477efdedb51427 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:28 p.m.