Triple
T27589405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OpenDaylight |
E699758
|
entity |
| Predicate | supportsBGP-LS |
P199262
|
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, supportsBGP-LS, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsBGP-LS Context triple: [OpenDaylight, supportsBGP-LS, 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.
supportsNETCONF
Indicates that one entity provides or is compatible with NETCONF (Network Configuration Protocol) functionality for another entity.
-
C.
supportsClasslessRouting
Indicates that an entity is capable of handling routing without relying on classful IP address boundaries, typically using subnet masks or CIDR for route determination.
-
D.
supportsNSSA
Indicates that one entity provides assistance, resources, or advocacy to uphold, maintain, or advance the goals, operations, or initiatives of the NSSA.
-
E.
supportsRelayAgents
Indicates that one entity is capable of working with or providing functionality for relay agents that forward or mediate communications between other entities.
- 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_69ff29d831b881908d485609e0fc1d0b |
completed | May 9, 2026, 12:34 p.m. |
| PD | Predicate disambiguation | batch_69ff28f9f9e4819087f3402735de66c7 |
completed | May 9, 2026, 12:30 p.m. |
| PDg | Predicate description generation | batch_69ff29d77f48819085304ed5e92eb906 |
completed | May 9, 2026, 12:34 p.m. |
Created at: April 27, 2026, 2:05 p.m.