Triple
T2088726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moore's law |
E32615
|
entity |
| Predicate | modernView |
P25075
|
FINISHED |
| Object | slowing of transistor scaling in recent process nodes |
—
|
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: slowing of transistor scaling in recent process nodes | Statement: [Moore's law, modernView, slowing of transistor scaling in recent process nodes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernView Context triple: [Moore's law, modernView, slowing of transistor scaling in recent process nodes]
-
A.
modernUse
Indicates how something is currently used or applied in modern times.
-
B.
modernStatus
Indicates the current or contemporary condition, classification, or standing of an entity in the present time.
-
C.
hasViewOnModernity
chosen
Indicates that an entity holds a particular perspective, stance, or interpretation regarding modernity.
-
D.
modernPractice
Indicates that an entity engages in or reflects a contemporary, up-to-date way of doing something, following current methods, standards, or trends.
-
E.
nearModernSite
Indicates that one entity is located in close physical proximity to a site or location from the modern era.
- 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_69a885eba0708190999696a45cbec816 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abba712388819091d68a4bb99f6b17 |
completed | March 7, 2026, 5:41 a.m. |
| PD | Predicate disambiguation | batch_69abb7b4356881909217c42ccb8bb1ed |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.