Triple

T29882831
Position Surface form Disambiguated ID Type / Status
Subject LEGO Mindstorms Robotics Invention System E758927 entity
Predicate mainController P18495 FINISHED
Object RCX programmable brick 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: RCX programmable brick | Statement: [LEGO Mindstorms Robotics Invention System, mainController, RCX programmable brick]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mainController
Context triple: [LEGO Mindstorms Robotics Invention System, mainController, RCX programmable brick]
  • A. mainPresenter
    Indicates that one entity serves as the primary or lead presenter for another entity, such as an event, program, or presentation.
  • B. mainFunctions chosen
    Indicates that the subject serves as the primary or central functional component or role for the object.
  • C. mainEntranceOn
    Indicates that the primary entrance of one entity is located on or faces toward another entity, such as a particular side, street, or boundary.
  • D. mainRite
    Indicates that one ritual, ceremony, or rite is the primary or central rite associated with a given context, entity, or event.
  • E. mainStartingPoint
    Indicates the primary location or position from which an event, process, or path begins.
  • F. None of above.

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_69f2245de2f48190a481404896b56254 completed April 29, 2026, 3:31 p.m.
NER Named-entity recognition batch_69f739a638748190808e7a2930dce16e completed May 3, 2026, 12:03 p.m.
PD Predicate disambiguation batch_69f732f2dc6c8190a4e86da98cc5eb05 completed May 3, 2026, 11:35 a.m.
Created at: April 29, 2026, 5:58 p.m.