Triple
T37661017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HAT add-on boards |
E937717
|
entity |
| Predicate | connectVia |
P37306
|
FINISHED |
| Object | 40-pin GPIO header |
—
|
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: 40-pin GPIO header | Statement: [HAT add-on boards, connectVia, 40-pin GPIO header]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectVia Context triple: [HAT add-on boards, connectVia, 40-pin GPIO header]
-
A.
connectionTo
chosen
Indicates a relationship in which one entity is linked, associated, or otherwise related to another entity.
-
B.
connectionStandard
Indicates the technical standard or protocol that defines how a connection between entities is established and operates.
-
C.
connectsBeyond
Indicates a relationship where one entity forms a link or association that extends past a usual boundary, scope, or intermediary to reach another entity.
-
D.
connectsMine
Indicates that one entity is linked or joined to another entity in the context of a mine or mining-related structure.
-
E.
connectsWorks
Indicates a relationship where one work serves to link, bridge, or associate two or more other works.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fffbb5d0188190b6d168de8626ff68 |
completed | May 10, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69fffa3bc1208190a277961385a4789f |
completed | May 10, 2026, 3:23 a.m. |
Created at: May 3, 2026, 4:18 p.m.