Triple
T30015754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BeagleBone Black |
E762589
|
entity |
| Predicate | communitySupported |
P127731
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [BeagleBone Black, communitySupported, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communitySupported Context triple: [BeagleBone Black, communitySupported, true]
-
A.
supportsCommunity
Indicates that one entity provides assistance, resources, or encouragement that benefits a community or group.
-
B.
hasCommunitySupport
chosen
Indicates that an entity is backed, endorsed, or positively received by a community or group of users.
-
C.
communityOwned
Indicates that something is collectively owned, managed, or controlled by a community rather than by an individual or private entity.
-
D.
communityBased
Indicates that something is organized, developed, or delivered within and by a local community, emphasizing local participation, control, and context.
-
E.
supportsCommunityContent
Indicates that an entity enables, hosts, or facilitates content created and shared by its user or community base.
- 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_69f2246b0c84819094f1250b6a02d277 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6a0ea04888190ac3a813b603bcb5c |
completed | May 3, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 6:45 p.m.