Triple
T17517474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESP8266 |
E426602
|
entity |
| Predicate | supportsStationMode |
P127729
|
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, supportsStationMode, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsStationMode Context triple: [ESP8266, supportsStationMode, yes]
-
A.
hasStationManagement
Indicates that one entity is responsible for managing, operating, or overseeing the activities and administration of a station associated with another entity.
-
B.
supportsSingleFrequencyNetworks
Indicates that an entity enables or is compatible with operating in single frequency networks, where multiple transmitters use the same frequency to provide coordinated coverage.
-
C.
wirelessStandalone
Indicates that something operates wirelessly on its own, without needing to be connected to or dependent on another device or system.
-
D.
hasStationFunction
Indicates that an entity serves in a particular functional role or capacity at a station.
-
E.
hasStations
Indicates that one entity possesses, contains, or is associated with one or more stations.
- 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.