Triple
T15740251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 555 timer IC |
E381582
|
entity |
| Predicate | hasDualVersion |
P28478
|
FINISHED |
| Object | 556 timer IC |
—
|
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: 556 timer IC | Statement: [555 timer IC, hasDualVersion, 556 timer IC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDualVersion Context triple: [555 timer IC, hasDualVersion, 556 timer IC]
-
A.
hasMultipleVersions
chosen
Indicates that an entity exists in more than one distinct version or revision.
-
B.
isDubVersionOf
Indicates that one audiovisual work is a dubbed version of another, with its original audio replaced by a different language track while preserving the original content.
-
C.
dualLicensed
Indicates that an entity is simultaneously licensed under two distinct licenses or licensing regimes.
-
D.
supportsDualSIM
Indicates that one entity provides or enables the use of two SIM cards simultaneously or interchangeably in another entity.
-
E.
hasVersionIn
Indicates that one entity exists as a specific version or variant within the context, format, or system represented by another entity.
- 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.