Triple

T14439761
Position Surface form Disambiguated ID Type / Status
Subject Quarkus E358055 entity
Predicate developer P73 FINISHED
Object Red Hat E5668 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: Red Hat | Statement: [Quarkus, developer, Red Hat]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Red Hat
Context triple: [Quarkus, developer, Red Hat]
  • A. Red Hat chosen
    Red Hat is a leading American open-source software company best known for its enterprise Linux distribution and related cloud and middleware solutions.
  • B. Red Hat Enterprise Linux
    Red Hat Enterprise Linux is a commercially supported, enterprise-grade Linux distribution widely used for servers, cloud deployments, and mission-critical applications.
  • C. SUSE
    SUSE is a German-based open-source software company best known for its enterprise Linux distributions and related infrastructure solutions.
  • D. Azul Systems
    Azul Systems is a software company specializing in high-performance, scalable Java runtimes and JVM technologies for enterprise applications.
  • E. Novell
    Novell was a prominent software company best known for its NetWare network operating system and contributions to enterprise networking and Linux technologies.
  • 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_69d8279402a88190821ffa39ae15bccf completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de914c1398819090fa2a74d257ba3e completed April 14, 2026, 7:11 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd5bda6ee88190aeec77092eb3576a completed May 8, 2026, 3:43 a.m.
Created at: April 10, 2026, 1:18 a.m.