Triple
T27589401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OpenDaylight |
E699758
|
entity |
| Predicate | supportsNorthboundAPIs |
P199188
|
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, supportsNorthboundAPIs, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsNorthboundAPIs Context triple: [OpenDaylight, supportsNorthboundAPIs, true]
-
A.
hasNorthboundPlatform
Indicates that an entity includes or is associated with a platform designated for northbound travel or service.
-
B.
hasNorthboundServicesTo
Indicates that an entity provides or supports services that travel or operate in a northbound direction to another location or entity.
-
C.
hasSouthboundPlatform
Indicates that an entity includes or is associated with a platform designated for southbound travel or service.
-
D.
hasSouthboundServicesTo
Indicates that a location provides transportation services traveling in a generally southward direction to another location.
-
E.
supportsAPIClientSDKs
Indicates that an entity provides or is compatible with software development kits (SDKs) intended for use by API clients.
- 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_69ff255b84788190a94682f4efe1d0b8 |
completed | May 9, 2026, 12:15 p.m. |
| PD | Predicate disambiguation | batch_69ff24f3ab108190bb017a656cff3d82 |
completed | May 9, 2026, 12:13 p.m. |
| PDg | Predicate description generation | batch_69ff255abca881908ef7635bd2e5af98 |
completed | May 9, 2026, 12:15 p.m. |
Created at: April 27, 2026, 2:05 p.m.