Triple
T25741468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel Lakefield |
E648228
|
entity |
| Predicate | hybridDesign |
P1529
|
FINISHED |
| Object | big.LITTLE-like |
—
|
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: big.LITTLE-like | Statement: [Intel Lakefield, hybridDesign, big.LITTLE-like]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hybridDesign Context triple: [Intel Lakefield, hybridDesign, big.LITTLE-like]
-
A.
designedWith
Indicates that one entity was created, planned, or developed using another entity as a tool, method, or guiding basis in its design process.
-
B.
parallelDesignTo
Indicates that one design is parallel or analogous to another in structure, function, or conceptual approach.
-
C.
hasDesign
chosen
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
-
D.
designCompromiseFor
Indicates a relationship where a design is adjusted or balanced to reach a compromise that addresses the needs, constraints, or preferences of a particular entity or situation.
-
E.
designedFeature
Indicates that one entity is a feature or component intentionally planned, created, or specified by another entity as part of a design.
- 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_69e7ab306eec8190b05c312c6ab186b8 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fd1b3010819098da2e7d46dfc326 |
completed | May 2, 2026, 1:33 p.m. |
| PD | Predicate disambiguation | batch_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 3:43 a.m.