Triple
T8284254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zephyr RTOS |
E193752
|
entity |
| Predicate | supports |
P516
|
FINISHED |
| Object | MQTT protocol |
E183382
|
NE 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: MQTT protocol | Statement: [Zephyr RTOS, supports, MQTT protocol]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MQTT protocol Context triple: [Zephyr RTOS, supports, MQTT protocol]
-
A.
MQTT
chosen
MQTT is a lightweight, publish-subscribe messaging protocol commonly used for reliable communication in IoT and constrained network environments.
-
B.
MQT
MQT is the IATA airport code for Sawyer International Airport, a public airport serving the Marquette, Michigan area in the United States.
-
C.
Qpid
Qpid is an open-source messaging system implementing the AMQP protocol, commonly used as a message broker in distributed and cloud-based applications.
-
D.
AMQP
AMQP (Advanced Message Queuing Protocol) is an open standard application layer protocol for message-oriented middleware that enables reliable, interoperable messaging between distributed systems.
-
E.
Modbus
Modbus is a widely used serial communication protocol in industrial automation systems for connecting electronic devices and transmitting data between controllers and field instruments.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca82e217a48190880695635c44b2ed |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7ad0535081908bb234cfc0e32b32 |
completed | March 31, 2026, 7:42 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cd687e64a08190a45a1cf5f5c32291 |
completed | April 1, 2026, 6:48 p.m. |
Created at: March 30, 2026, 5:52 p.m.