Triple
T25741470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel Lakefield |
E648228
|
entity |
| Predicate | bigCoreType |
P18973
|
FINISHED |
| Object | Sunny Cove |
—
|
NE NERFINISHED |
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: Sunny Cove | Statement: [Intel Lakefield, bigCoreType, Sunny Cove]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bigCoreType Context triple: [Intel Lakefield, bigCoreType, Sunny Cove]
-
A.
bigCoreCount
Indicates that an entity (such as a processor or system) has a relatively large number of cores compared to a typical or baseline configuration.
-
B.
typicalCoreType
chosen
Indicates that something is a standard or characteristic core type within a given classification or system.
-
C.
majorType
Indicates that one entity is classified as the primary or main type/category of another entity.
-
D.
bigThreeWith
Indicates a relationship where three entities are grouped or associated together as a primary or most significant trio in a given context.
-
E.
coreUnitType
Indicates that one entity is classified as the primary or fundamental type/category to which another entity (a core unit) belongs.
- 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.