Triple
T28582894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zephyr |
E723423
|
entity |
| Predicate | supportsMQTT |
P202947
|
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, supportsMQTT, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMQTT Context triple: [Zephyr, supportsMQTT, true]
-
A.
supportsPort
Indicates that one entity is capable of handling, providing, or being compatible with a specified port or port configuration.
-
B.
supportsBridging
Indicates that one entity enables or facilitates a bridging connection or transition between two otherwise separate entities, systems, or contexts.
-
C.
supportsTopic
Indicates that one entity provides backing, endorsement, or assistance for a particular topic, idea, or subject.
-
D.
isSupportedBy
Indicates that an entity is upheld, sustained, or enabled by another entity, which provides necessary assistance, resources, or justification.
-
E.
supportsTerminalConnections
Indicates that one entity is capable of handling or enabling direct connections to terminal interfaces or endpoints.
- 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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a00d508290081909f3d5dfbb2e80c8e |
completed | May 10, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_6a00d49da4cc81909566ad286ec22292 |
completed | May 10, 2026, 6:55 p.m. |
| PDg | Predicate description generation | batch_6a00d5073e188190b09916119a9c032d |
completed | May 10, 2026, 6:57 p.m. |
Created at: April 28, 2026, 4:16 a.m.