Triple
T3800161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mini DisplayPort |
E91667
|
entity |
| Predicate | signalDirection |
P30196
|
FINISHED |
| Object | unidirectional from source to sink |
—
|
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: unidirectional from source to sink | Statement: [Mini DisplayPort, signalDirection, unidirectional from source to sink]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signalDirection Context triple: [Mini DisplayPort, signalDirection, unidirectional from source to sink]
-
A.
circuitDirection
Indicates the orientation or flow direction of a circuit or circuit path relative to its components or layout.
-
B.
signalPolarity
Indicates the directional orientation or sign (positive or negative) of a signal relative to a defined reference.
-
C.
hasDirectionType
chosen
Indicates that something possesses or is associated with a specific type or category of direction.
-
D.
containsDirectionOf
Indicates that one entity includes or encompasses the directional orientation or path associated with another entity.
-
E.
directionalDesignation
Indicates a relationship where one entity is assigned or labeled with a specific directional orientation relative to another entity or reference frame.
- 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_69aed96354f48190a768966d6bd19b04 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aee8db8a288190afd1e3b9dcf02e97 |
completed | March 9, 2026, 3:35 p.m. |
| PD | Predicate disambiguation | batch_69aee7461abc8190945716f4b93e1a18 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:15 p.m.