Triple
T27589404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OpenDaylight |
E699758
|
entity |
| Predicate | supportsNETCONF |
P199246
|
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, supportsNETCONF, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsNETCONF Context triple: [OpenDaylight, supportsNETCONF, true]
-
A.
supportsNorthboundAPIs
Indicates that one entity provides or is compatible with northbound APIs used by higher-level systems or applications to interact with it.
-
B.
hasNetworkElement
Indicates that one entity includes, contains, or is associated with a specific network element as part of its network structure or configuration.
-
C.
supportsNetworkVirtualization
Indicates that one entity provides capabilities or functionality that enable network virtualization for another entity or within a system.
-
D.
supportsHostManagement
Indicates that an entity provides functionality to manage, configure, or control a host system or environment.
-
E.
supportedNetwork
Indicates that one entity (such as a device, service, or application) is compatible with, operates on, or is designed to work over a specified network or type of network.
- F. None of above. chosen
Provenance (4 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_69ff289541e0819096eeceb8e6332650 |
completed | May 9, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69ff281ab1988190920f0443be9f10cc |
completed | May 9, 2026, 12:27 p.m. |
| PDg | Predicate description generation | batch_69ff28948b34819090e7e8b0b19535b2 |
completed | May 9, 2026, 12:29 p.m. |
Created at: April 27, 2026, 2:05 p.m.