Triple
T27589400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OpenDaylight |
E699758
|
entity |
| Predicate | supportsInteroperability |
P48644
|
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, supportsInteroperability, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsInteroperability Context triple: [OpenDaylight, supportsInteroperability, true]
-
A.
isDesignedForInteroperability
Indicates that something is intended or configured to work seamlessly and compatibly with other systems, components, or standards.
-
B.
interoperabilityWith
chosen
Indicates that one system, component, or standard can effectively exchange and use information or services with another.
-
C.
interoperabilityLevel
Indicates the degree to which different systems, components, or standards can effectively work together and exchange information.
-
D.
interoperabilityStandard
Indicates that there is a standard or specification enabling different systems, components, or technologies to work together and exchange information seamlessly.
-
E.
supportsInterconnection
Indicates that one entity enables, facilitates, or maintains a connection or interoperability between two or more other entities.
- 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_69ff246e0d4481908bcec718e1d4025b |
completed | May 9, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69ff23cb70ac81909b776ace4597ae9c |
completed | May 9, 2026, 12:08 p.m. |
Created at: April 27, 2026, 2:05 p.m.