Triple

T27589438
Position Surface form Disambiguated ID Type / Status
Subject OpenDaylight E699758 entity
Predicate supportsNorthboundInterfaceType P199188 FINISHED
Object REST 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: REST | Statement: [OpenDaylight, supportsNorthboundInterfaceType, REST]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsNorthboundInterfaceType
Context triple: [OpenDaylight, supportsNorthboundInterfaceType, REST]
  • A. supportsNorthboundAPIs chosen
    Indicates that one entity provides or is compatible with northbound APIs used by higher-level systems or applications to interact with it.
  • B. supportsSouthboundAPIs
    Indicates that an entity provides or is compatible with southbound APIs used to communicate with and control lower-layer or downstream systems or devices.
  • C. hasNorthboundPlatform
    Indicates that an entity includes or is associated with a platform designated for northbound travel or service.
  • D. hasNorthboundServicesTo
    Indicates that an entity provides or supports services that travel or operate in a northbound direction to another location or entity.
  • E. hasSouthboundPlatform
    Indicates that an entity includes or is associated with a platform designated for southbound travel or service.
  • 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_69ff32b88bf48190b45afd1b60cb511c completed May 9, 2026, 1:12 p.m.
PD Predicate disambiguation batch_69ff3031e18881908927b2ab452de863 completed May 9, 2026, 1:01 p.m.
Created at: April 27, 2026, 2:05 p.m.