Triple
T8611445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | eMMC |
E203921
|
entity |
| Predicate | connectionToHost |
P15300
|
FINISHED |
| Object | soldered directly to PCB |
—
|
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: soldered directly to PCB | Statement: [eMMC, connectionToHost, soldered directly to PCB]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectionToHost Context triple: [eMMC, connectionToHost, soldered directly to PCB]
-
A.
connectionTo
Indicates a relationship in which one entity is linked, associated, or otherwise related to another entity.
-
B.
connectionEstablishmentMethod
chosen
Indicates the method or mechanism by which a connection between entities is initiated or established.
-
C.
connectsWithin
Indicates that one entity establishes a connection or link between elements that lie inside the bounds or scope of another entity.
-
D.
connectionPort
Indicates a specific port through which two components, systems, or devices are connected or can communicate.
-
E.
networkHost
Indicates that one entity serves as the host machine or node on which another networked entity (such as a service, application, or connection) resides or operates.
- 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_69ca832c23e4819095a9f3eea4a21828 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46fc31e08190aab5ab8f92f3315c |
completed | March 31, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cc455437488190b7506f820daf6e32 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:25 p.m.