Triple
T17517454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESP8266 |
E426602
|
entity |
| Predicate | requiresExternalFlash |
P127727
|
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, requiresExternalFlash, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresExternalFlash Context triple: [ESP8266, requiresExternalFlash, yes]
-
A.
requiresFirmware
Indicates that one entity depends on specific firmware being present or installed on another entity in order to function or be valid.
-
B.
usesFinFlash
Indicates that one entity employs or displays a fin-based flashing signal or pattern in relation to another entity.
-
C.
hasOnboardFlash
Indicates that an entity is equipped with built-in flash memory as part of its hardware.
-
D.
requiresDevice
Indicates that performing the specified action or relationship is contingent on the presence or use of a particular device.
-
E.
typicalFlashFootprint
Indicates the usual spatial extent or area on a surface that is illuminated by a flash under normal operating conditions.
- 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_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. |
| PDg | Predicate description generation | batch_69e3bbb37d148190b7f38599c06594ee |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:49 a.m.