Triple

T17558098
Position Surface form Disambiguated ID Type / Status
Subject AMQP E427634 entity
Predicate hasVersion P455 FINISHED
Object AMQP 0-9-1 NE NERFINISHED

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 0-9-1 | Statement: [AMQP, hasVersion, AMQP 0-9-1]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: AMQP 0-9-1
Context triple: [AMQP, hasVersion, AMQP 0-9-1]
  • 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. RabbitMQ
    RabbitMQ is an open-source message broker that implements the Advanced Message Queuing Protocol (AMQP) to enable reliable, scalable communication between distributed applications and services.
  • 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. ActiveMQ Artemis
    ActiveMQ Artemis is a high-performance, multi-protocol, open-source message broker developed under the Apache ActiveMQ project, designed for low-latency, reliable messaging in enterprise systems.
  • E. ActiveMQ
    ActiveMQ is an open-source message broker written in Java that supports multiple messaging protocols and enables reliable, asynchronous communication between distributed applications.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d889df6dc081908f67dbadc03c07ee completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e4562413d08190acaa5272046d3626 completed April 19, 2026, 4:12 a.m.
Created at: April 10, 2026, 5:50 a.m.