Triple
T13319835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MOSFET |
E317284
|
entity |
| Predicate | inventedFor |
P11902
|
FINISHED |
| Object | high-density integrated circuits |
—
|
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: high-density integrated circuits | Statement: [MOSFET, inventedFor, high-density integrated circuits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inventedFor Context triple: [MOSFET, inventedFor, high-density integrated circuits]
-
A.
wasInventedBy
Indicates that something (typically an object, concept, or process) was created or brought into existence by a particular inventor or originator.
-
B.
originallyDevelopedFor
chosen
Indicates that something was first created, designed, or produced with the primary purpose of serving a particular use, user group, context, or application.
-
C.
invention
Indicates that one entity is the creator or originator of another entity, typically a device, method, or idea.
-
D.
inventionType
Indicates the specific category or kind of invention that characterizes the relationship between an invention and its type.
-
E.
firstWidelyUsedFor
Indicates that something was the earliest instance to be broadly adopted or commonly used for a particular purpose or application.
- 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_69d806b4d62c81908d4ced1665414be5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6babd88190a5d529df9584b9a4 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:29 p.m.