Triple
T31733326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CMOS technology |
E809918
|
entity |
| Predicate | dominantFor |
P29628
|
FINISHED |
| Object | digital VLSI design |
—
|
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: digital VLSI design | Statement: [CMOS technology, dominantFor, digital VLSI design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantFor Context triple: [CMOS technology, dominantFor, digital VLSI design]
-
A.
dominantOn
Indicates that one entity exerts control, authority, or prevailing influence over another in a given context.
-
B.
dominantDuring
Indicates that one entity holds a prevailing or controlling influence over another specifically within a given time period or interval.
-
C.
dominantForm
chosen
Indicates that one form, type, or variant is the primary or most prevalent version relative to others in a given context.
-
D.
dominantComplex
Indicates that one entity exerts primary control, influence, or prominence over another within a given context or system.
-
E.
dominantUntil
Indicates that one entity maintains dominance over another up to, but not beyond, a specified point or condition in time.
- 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_69f348e0e4908190a884582eca646fb7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: April 30, 2026, 11:22 p.m.