Triple
T15740228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 555 timer IC |
E381582
|
entity |
| Predicate | voltageDividerRatio |
P507
|
FINISHED |
| Object | 1:3:2 |
—
|
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: 1:3:2 | Statement: [555 timer IC, voltageDividerRatio, 1:3:2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voltageDividerRatio Context triple: [555 timer IC, voltageDividerRatio, 1:3:2]
-
A.
radiusRatio
Indicates the proportional relationship between one radius and another, typically expressing how large one is relative to the other.
-
B.
dividedBy
Indicates that one quantity is separated into a specified number of equal parts or groups by another quantity, representing a division relationship between them.
-
C.
subunitRatio
chosen
Indicates the proportional relationship between the quantities or sizes of different subunits within a larger whole.
-
D.
relatedDivide
Indicates that one entity divides or partitions another entity in a way that is contextually or relationally significant, rather than purely numerical.
-
E.
divisionResultOf
Indicates that one quantity is the numerical result obtained by dividing another quantity by a specified divisor.
- 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_69d86d9cdb648190bf3171be0bd7d872 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4d6b5788190883746ee82c799f5 |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e0052c6208819098165d61d378d13b |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:46 a.m.