Triple

T7033863
Position Surface form Disambiguated ID Type / Status
Subject JRun E163331 entity
Predicate supportsProtocol P203 FINISHED
Object IIOP E341115 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: IIOP | Statement: [JRun, supportsProtocol, IIOP]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: IIOP
Context triple: [JRun, supportsProtocol, IIOP]
  • A. IIOP chosen
    IIOP (Internet Inter-ORB Protocol) is a network protocol used by CORBA to enable communication between distributed objects across different platforms and programming languages.
  • B. ONC RPC
    ONC RPC (Open Network Computing Remote Procedure Call) is a widely used remote procedure call protocol developed by Sun Microsystems that enables networked applications to communicate and invoke procedures on remote systems in a platform-independent way.
  • C. RMI
    RMI is an institute at the University of California, Davis dedicated to research, education, and outreach in wine, food science, and related disciplines.
  • D. RMI
    RMI is the commonly used abbreviation for the Republic of the Marshall Islands, a Pacific island nation composed of atolls and islands.
  • E. OPC
    OPC (OLE for Process Control) is an industrial communication standard that enables interoperability and data exchange between control devices, sensors, and software applications in automation systems.
  • 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_69c6885d691c81908cf7d31083113886 completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6e2118fc88190a0751ca18eafb4a5 completed March 27, 2026, 8:01 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7759c8e408190a7d457e77a44ee26 completed March 28, 2026, 6:30 a.m.
Created at: March 27, 2026, 2:36 p.m.