Triple

T27589399
Position Surface form Disambiguated ID Type / Status
Subject OpenDaylight E699758 entity
Predicate supportsProgrammability P76293 FINISHED
Object true LITERAL 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: true | Statement: [OpenDaylight, supportsProgrammability, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsProgrammability
Context triple: [OpenDaylight, supportsProgrammability, true]
  • A. programmability chosen
    Indicates that an entity can be configured, controlled, or modified through programming or code to change its behavior or functions.
  • B. supportsProgramType
    Indicates that one entity is capable of handling, offering, or being compatible with a specified type of program.
  • C. hasProgrammingModel
    Indicates that one entity defines, specifies, or is associated with the programming model used or supported by another entity.
  • D. supportsProgramOf
    Indicates that one entity provides assistance, resources, or endorsement to help another entity’s program operate or succeed.
  • E. supportsProgrammingArtifact
    Indicates that one entity provides the necessary functionality, environment, or resources for a programming-related artifact (such as code, tools, or frameworks) to operate or be effectively used.
  • 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_69ef6a4d71f081909a1235763206b691 completed April 27, 2026, 1:53 p.m.
NER Named-entity recognition batch_69ff234f32888190a1d800a3bda432eb completed May 9, 2026, 12:06 p.m.
PD Predicate disambiguation batch_69ff228ae9a0819083f4b97c10b923f4 completed May 9, 2026, 12:03 p.m.
Created at: April 27, 2026, 2:05 p.m.