Triple
T28607931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STM32 series boards |
E724101
|
entity |
| Predicate | hasRepresentativeBoard |
P199949
|
FINISHED |
| Object | Nucleo boards |
—
|
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: Nucleo boards | Statement: [STM32 series boards, hasRepresentativeBoard, Nucleo boards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRepresentativeBoard Context triple: [STM32 series boards, hasRepresentativeBoard, Nucleo boards]
-
A.
hasRepresentativeBody
Indicates that an entity is associated with or governed by a specific representative body that acts or decides on its behalf.
-
B.
governingBodyRepresents
Indicates that a governing body acts on behalf of, and makes decisions representing the interests or authority of, another entity.
-
C.
isBoardOf
Indicates that an entity serves as the governing board or board member for another entity (such as an organization, company, or institution).
-
D.
boardMembersRepresent
Indicates that designated board members act on behalf of, and in the interests of, a particular organization or group.
-
E.
hasTypeOfRepresentative
Indicates that one entity serves as a specific kind or category of representative for another entity.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69ff65987ff88190b09be64f7c0e1da9 |
completed | May 9, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69ff6525b0548190bef7a9f009e00bb8 |
completed | May 9, 2026, 4:47 p.m. |
| PDg | Predicate description generation | batch_69ff659717708190bb56714d1b261063 |
completed | May 9, 2026, 4:49 p.m. |
Created at: April 28, 2026, 4:28 a.m.