Triple
T17517485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESP8266 |
E426602
|
entity |
| Predicate | hasCommunitySupport |
P127731
|
FINISHED |
| Object | large global community |
—
|
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: large global community | Statement: [ESP8266, hasCommunitySupport, large global community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommunitySupport Context triple: [ESP8266, hasCommunitySupport, large global community]
-
A.
supportsCommunity
Indicates that one entity provides assistance, resources, or encouragement that benefits a community or group.
-
B.
supportsCommunityContent
Indicates that an entity enables, hosts, or facilitates content created and shared by its user or community base.
-
C.
hasComponentCommunity
Indicates that an entity includes or is composed of a specific community as one of its constituent parts.
-
D.
hasCommunityIn
Indicates that a community is present, active, or established within a specified location, platform, or context.
-
E.
hasCommunityResource
Indicates that an entity provides, contains, or is associated with a resource intended for use by a community.
- 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.