Triple
T6408751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OASIS |
E127653
|
entity |
| Predicate | standardDeveloped |
P1371
|
FINISHED |
| Object | AMQP |
E427634
|
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: AMQP | Statement: [OASIS, standardDeveloped, AMQP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: AMQP Context triple: [OASIS, standardDeveloped, AMQP]
-
A.
AMQP
chosen
AMQP (Advanced Message Queuing Protocol) is an open standard application layer protocol for message-oriented middleware that enables reliable, interoperable messaging between distributed systems.
-
B.
JMS
JMS (Java Message Service) is a Java API specification that enables applications to create, send, receive, and read messages in a loosely coupled, asynchronous, and reliable messaging system.
-
C.
ZeroMQ
ZeroMQ is a high-performance asynchronous messaging library that provides lightweight, flexible sockets for building scalable distributed and concurrent applications.
-
D.
MQTT
MQTT is a lightweight, publish-subscribe messaging protocol commonly used for reliable communication in IoT and constrained network environments.
-
E.
MSMQ
MSMQ (Microsoft Message Queuing) is a Microsoft messaging technology that enables reliable, asynchronous communication between distributed applications by queuing messages.
- 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_69c0083723d88190b1e37b19df162c08 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c068cdf25881908d42a5d979637ad6 |
completed | March 22, 2026, 10:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c638b38c888190aa2433173db64c90 |
completed | March 27, 2026, 7:58 a.m. |
Created at: March 22, 2026, 4:41 p.m.