Triple
T17517491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESP8266 |
E426602
|
entity |
| Predicate | supportsOTAUpdates |
P83889
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [ESP8266, supportsOTAUpdates, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsOTAUpdates Context triple: [ESP8266, supportsOTAUpdates, yes]
-
A.
supportsOTA
chosen
Indicates that one entity enables or is compatible with over-the-air (OTA) updates or operations for another entity.
-
B.
supportsOneClickUpdates
Indicates that an entity enables or is compatible with performing updates through a streamlined, single-action (one-click) process.
-
C.
softwareUpdatable
Indicates that a software system or component can be modified or upgraded after deployment, typically through patches, updates, or new versions.
-
D.
softwareUpdateModel
Indicates that one entity serves as the model, specification, or type definition used to perform or describe a software update on another entity.
-
E.
firmwareUpgradable
Indicates that a device’s firmware can be updated or replaced after deployment, typically through software-based upgrade mechanisms.
- 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_69d889dd9164819087b1dc3c9240c870 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e452615a8481909974e9855ea7a8e4 |
completed | April 19, 2026, 3:56 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f5fbcc8190a6ea9639bf5650da |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:49 a.m.