Triple
T22493810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Device Provisioning Protocol |
E556085
|
entity |
| Predicate | canProvision |
P79900
|
FINISHED |
| Object | headless IoT devices |
—
|
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: headless IoT devices | Statement: [Device Provisioning Protocol, canProvision, headless IoT devices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canProvision Context triple: [Device Provisioning Protocol, canProvision, headless IoT devices]
-
A.
hasProvisionOn
Indicates that one entity contains, specifies, or includes a particular provision, clause, or stipulation concerning another entity or subject.
-
B.
hasOnlineProvision
Indicates that an entity offers or supports a service, feature, or function through an online or internet-based channel.
-
C.
canEnable
Indicates that one entity has the capability or authority to activate, turn on, or make another entity or function operational.
-
D.
supportsProvisioningMethod
chosen
Indicates that one entity is capable of using or is compatible with a particular provisioning method offered or required by another entity.
-
E.
invokesProvision
Indicates that one entity calls upon, activates, or applies a specific provision, rule, or clause within a broader framework such as a contract, policy, or statute.
- 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_69e11e5445bc8190b6a9481926db3355 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15cb0dfb88190a4175e5e95d7ad4b |
completed | April 29, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69e898be31448190be5ae7f5656f0497 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:49 p.m.