Triple
T4436611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G.729 |
E95665
|
entity |
| Predicate | algorithmicDelay |
P56007
|
FINISHED |
| Object | 15 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: 15 ms | Statement: [G.729, algorithmicDelay, 15 ms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: algorithmicDelay Context triple: [G.729, algorithmicDelay, 15 ms]
-
A.
communicationLatency
Indicates the time delay between when a communication is sent by one entity and when it is received or processed by another.
-
B.
delayedUntil
Indicates that the occurrence or effect of one event or condition is postponed and does not take place until a specified later event, time, or condition is reached.
-
C.
mayDelay
Indicates that one entity has the potential or permission to cause a postponement or slowing of another entity, event, or process.
-
D.
congestionControlAlgorithm
Indicates that one entity uses, implements, or is associated with a particular congestion control algorithm in managing network traffic.
-
E.
intendedDuration
Indicates the planned or expected length of time for which an action, event, or state is meant to occur or remain in effect.
- F. None of above. chosen
Provenance (4 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_69b3453ea2b48190a26f154b3b8fece5 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3558b1d4481909060ede5e0ded4bc |
completed | March 13, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69b34f6078cc8190831b89f404198cc5 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b3505a87b4819083fbbd58870e520b |
completed | March 12, 2026, 11:46 p.m. |
Created at: March 12, 2026, 11:31 p.m.