Triple
T29391283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adafruit Feather M0 boards |
E745373
|
entity |
| Predicate | batteryConnectorType |
P167142
|
FINISHED |
| Object | JST-PH 2-pin |
—
|
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: JST-PH 2-pin | Statement: [Adafruit Feather M0 boards, batteryConnectorType, JST-PH 2-pin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: batteryConnectorType Context triple: [Adafruit Feather M0 boards, batteryConnectorType, JST-PH 2-pin]
-
A.
chargingPortType
Indicates the specific kind of connector or interface used for charging a device.
-
B.
connectorType
Indicates the specific kind or category of connection interface that links two entities.
-
C.
batteryType
Indicates the specific kind or category of battery associated with or used by an entity.
-
D.
connectorTypeDesignation
Indicates the specific type or classification assigned to a connector within a connection or interface relationship.
-
E.
chargingPortLocation
Indicates the physical position or area on an object or device where its charging port is located.
- 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f669ff3b2081909ecfc701841c6532 |
completed | May 2, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f663ff176c8190aaadb475f75daee4 |
completed | May 2, 2026, 8:52 p.m. |
Created at: April 28, 2026, 2:42 p.m.