Triple
T26212667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel Core i3 |
E655528
|
entity |
| Predicate | firstMobileGenerationCodename |
P28419
|
FINISHED |
| Object | Arrandale |
—
|
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: Arrandale | Statement: [Intel Core i3, firstMobileGenerationCodename, Arrandale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstMobileGenerationCodename Context triple: [Intel Core i3, firstMobileGenerationCodename, Arrandale]
-
A.
codenameOfFirstGeneration
chosen
Indicates that one entity is the codename assigned to the first generation of another entity.
-
B.
secondGenerationCodename
Indicates that an entity is assigned or associated with a codename specifically used for its second generation or iteration.
-
C.
successorCodename
Indicates that one codename directly follows and replaces another in a sequence or lifecycle.
-
D.
hardwareCodename
Indicates that one entity is the internal or code name assigned to a particular hardware product or component.
-
E.
predecessorCoreCodename
Indicates that one core codename directly precedes another in a sequence or lineage of codenames.
- 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_69ee5b49adb4819086545280d4ef6337 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69fdee770af48190aca2670db50f8b49 |
completed | May 8, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69fdecec98a08190a357d816dc2a6dbe |
completed | May 8, 2026, 2:02 p.m. |
Created at: April 26, 2026, 8:53 p.m.