Triple
T19921590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DJI Avata |
E478807
|
entity |
| Predicate | videoTransmissionMaxBitrate |
P45736
|
FINISHED |
| Object | 50 Mbps |
—
|
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: 50 Mbps | Statement: [DJI Avata, videoTransmissionMaxBitrate, 50 Mbps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: videoTransmissionMaxBitrate Context triple: [DJI Avata, videoTransmissionMaxBitrate, 50 Mbps]
-
A.
maximumBitrate
chosen
Indicates the highest data transfer rate allowed or supported for a given media stream or connection.
-
B.
dvdVideoMaxBitrate
Indicates the maximum data transfer rate at which a DVD video stream can be encoded or played back.
-
C.
bluRayMaxBitrate
Indicates the maximum data transfer rate at which a Blu-ray disc or Blu-ray media stream can be encoded or played back.
-
D.
bitrateRange
Indicates the range of data transfer rates (minimum to maximum bitrate) within which something, such as a media stream or encoding, operates.
-
E.
hasMaxMacroblocksPerSecond
Indicates the maximum number of macroblocks that can be processed or handled per second in a given context.
- 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e659c6919c8190a96106532580b6b6 |
completed | April 20, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69e537f070b481908958e0e5911dcdc1 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.