Triple
T8612105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I2C |
E203934
|
entity |
| Predicate | dataDirectionControl |
P9929
|
FINISHED |
| Object | master-driven clock |
—
|
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: master-driven clock | Statement: [I2C, dataDirectionControl, master-driven clock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataDirectionControl Context triple: [I2C, dataDirectionControl, master-driven clock]
-
A.
dataFlowDirection
chosen
Indicates the direction in which data moves or is transmitted from a source entity to a target entity.
-
B.
dataControl
Indicates that one entity has the authority or capability to determine how another entity’s data is collected, used, shared, or managed.
-
C.
connectionDirection
Indicates the directional flow or orientation of a connection from one entity to another.
-
D.
containsDirectionOf
Indicates that one entity includes or encompasses the directional orientation or path associated with another entity.
-
E.
circuitDirection
Indicates the orientation or flow direction of a circuit or circuit path relative to its components or layout.
- 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_69cc46fdf21c81908ffc6363e98ab871 |
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.