Triple
T6408988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Real-time Transport Control Protocol |
E127658
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | control protocol |
C993
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: control protocol Context triple: [Real-time Transport Control Protocol, instanceOf, control protocol]
-
A.
export control law
Export control law is the body of legal rules and regulations that govern the transfer of goods, technology, software, and services across national borders to protect national security, foreign policy interests, and international obligations.
-
B.
control line
A control line is a designated boundary or reference line used to guide, regulate, or constrain the behavior, position, or operation of a system, process, or object.
-
C.
central control system
A central control system is a coordinating entity that monitors, manages, and directs the operations of interconnected components or subsystems to achieve overall system objectives.
-
D.
remote control
A remote control is a handheld device that wirelessly sends commands to operate electronic equipment from a distance.
-
E.
communication protocol
chosen
A communication protocol is a defined set of rules and formats that enable reliable, structured exchange of data between two or more communicating entities in a networked system.
- F. None of above.
Provenance (1 batch)
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_69c0083723d88190b1e37b19df162c08 |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 4:41 p.m.