Triple
T7980171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel Core m3-8100Y |
E185550
|
entity |
| Predicate | lithography |
P76106
|
FINISHED |
| Object | 14 nm |
—
|
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: 14 nm | Statement: [Intel Core m3-8100Y, lithography, 14 nm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lithography Context triple: [Intel Core m3-8100Y, lithography, 14 nm]
-
A.
fabricationTechnology
chosen
Indicates the manufacturing or production method used to create or realize an entity.
-
B.
printingOfWork
Indicates that one entity is a specific printing or print edition produced from a particular work.
-
C.
imprintsOn
Indicates that one entity forms a strong, often instinctive or formative attachment or bond to another, typically as a primary reference or guide.
-
D.
overprints
Indicates that one entity is printed or superimposed on top of another, partially or completely covering the underlying material or pattern.
-
E.
imprintedOn
Indicates that one entity has formed a strong, often early-life, attachment or bond to another entity, typically treating it as a primary reference or caregiver.
- 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_69ca829851908190b4e03829353ee7c3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c261904819086910898071f3629 |
completed | March 31, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69cb048009a08190b4c577208a9f8f76 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:14 p.m.