Triple
T26177905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel Core 2 |
E654591
|
entity |
| Predicate | codenameFamily |
P32834
|
FINISHED |
| Object | Penryn |
—
|
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: Penryn | Statement: [Intel Core 2, codenameFamily, Penryn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codenameFamily Context triple: [Intel Core 2, codenameFamily, Penryn]
-
A.
familyCodeName
Indicates a designated code name used to identify or refer to a family unit or family-related grouping.
-
B.
codenameOwner
Indicates that one entity is the designated owner or holder of the specified codename associated with another entity.
-
C.
relatedCodename
chosen
Indicates that one entity has an associated or connected codename that is contextually related to it.
-
D.
codenameOfFirstGeneration
Indicates that one entity is the codename assigned to the first generation of another entity.
-
E.
featuresFamilyName
Indicates that an entity is associated with or displays a particular family name.
- 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_69ee5b45873c81909499203612d05d07 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 26, 2026, 8:38 p.m.