Triple
T28582895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zephyr |
E723423
|
entity |
| Predicate | supportsCoAP |
P203
|
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: [Zephyr, supportsCoAP, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsCoAP Context triple: [Zephyr, supportsCoAP, true]
-
A.
supports6LoWPAN
Indicates that one entity provides compatibility with or functionality for the 6LoWPAN networking protocol for another entity.
-
B.
supportsMQTT
Indicates that an entity is capable of using or is compatible with the MQTT messaging protocol.
-
C.
supportsPort
Indicates that one entity is capable of handling, providing, or being compatible with a specified port or port configuration.
-
D.
supportsEP
Indicates that one entity provides assistance, resources, or endorsement to another entity’s emergency preparedness (EP) efforts or program.
-
E.
supportsFeature
chosen
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
- 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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a00d6aff0a08190a330dd0c7c1352f9 |
completed | May 10, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_6a00d60f2a508190aeaf5a9d8af9c39e |
completed | May 10, 2026, 7:01 p.m. |
Created at: April 28, 2026, 4:16 a.m.