Triple
T27589403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OpenDaylight |
E699758
|
entity |
| Predicate | supportsOpenFlow |
P199227
|
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, supportsOpenFlow, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsOpenFlow Context triple: [OpenDaylight, supportsOpenFlow, true]
-
A.
supportsFlowOf
Indicates that one entity facilitates, enables, or maintains the movement or progression of another entity (such as a substance, resource, or process).
-
B.
supportsOAM
Indicates that one entity provides compatibility with, or functional backing for, the Open Application Model (OAM) in relation to another entity.
-
C.
supportsNorthboundAPIs
Indicates that one entity provides or is compatible with northbound APIs used by higher-level systems or applications to interact with it.
-
D.
supportsTraffic
Indicates that one entity is capable of handling, carrying, or accommodating the flow or volume of traffic associated with another entity.
-
E.
supportsVLANTagging
Indicates that one entity provides the capability for another entity or interface to handle and process VLAN-tagged network traffic.
- 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_69ff27b125948190aced0fe0189fd39a |
completed | May 9, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69ff26c30a0481909ef6a54ded851e42 |
completed | May 9, 2026, 12:21 p.m. |
| PDg | Predicate description generation | batch_69ff27b0385c8190bccf340d26268f77 |
completed | May 9, 2026, 12:25 p.m. |
Created at: April 27, 2026, 2:05 p.m.