Triple
T30786585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WheatNet-IP |
E783970
|
entity |
| Predicate | audioNetworkingType |
P171599
|
FINISHED |
| Object | layer-3 audio-over-IP |
—
|
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: layer-3 audio-over-IP | Statement: [WheatNet-IP, audioNetworkingType, layer-3 audio-over-IP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audioNetworkingType Context triple: [WheatNet-IP, audioNetworkingType, layer-3 audio-over-IP]
-
A.
audioCodingType
Indicates the specific method or standard used to encode or compress an audio signal.
-
B.
audioChannelType
Indicates the specific role or configuration of an audio channel within a multi-channel audio setup (e.g., left, right, center, surround).
-
C.
audioTransmission
Indicates that an audio signal is being sent or conveyed from one entity (source) to another (destination) through some transmission medium or channel.
-
D.
audioStreaming
Indicates that one entity is transmitting audio data in real time for another entity to receive or play back.
-
E.
audioStandard
Indicates the audio format or specification standard that applies to the associated media or device.
- 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_69f224b213c8819083886073f90b647e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a1ac56b88190a820434b65c9fa23 |
completed | May 3, 2026, 1:15 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a0e920cc8190a943fdd0594906c5 |
completed | May 3, 2026, 1:12 a.m. |
Created at: April 29, 2026, 8:41 p.m.