Triple
T1854596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chromebit |
E41672
|
entity |
| Predicate | connectivityInterface |
P1374
|
FINISHED |
| Object | HDMI |
—
|
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: HDMI | Statement: [Chromebit, connectivityInterface, HDMI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectivityInterface Context triple: [Chromebit, connectivityInterface, HDMI]
-
A.
connectivity
Indicates...the existence, degree, or quality of a link or communication pathway between entities, allowing interaction or information flow between them.
-
B.
connectorType
chosen
Indicates the specific kind or category of connection interface that links two entities.
-
C.
connectsTo
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
D.
networkType
Indicates the category or kind of network associated with or used by an entity (e.g., wired, wireless, virtual, or specific protocol-based networks).
-
E.
connectsDeviceType
Indicates a relationship where one entity is associated with or linked to a specific type or category of device.
- 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_69a8864a83848190a4ec02721306c511 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb231de14819091da3a20ed03c430 |
completed | March 7, 2026, 5:05 a.m. |
| PD | Predicate disambiguation | batch_69abafde4598819099d8229128348fd3 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.