Triple
T26036371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel Pentium III |
E647561
|
entity |
| Predicate | familyModel |
P164191
|
FINISHED |
| Object | Pentium III Xeon |
—
|
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: Pentium III Xeon | Statement: [Intel Pentium III, familyModel, Pentium III Xeon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyModel Context triple: [Intel Pentium III, familyModel, Pentium III Xeon]
-
A.
familyGroup
Indicates that multiple entities are related to each other as members of the same family unit or household.
-
B.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
-
C.
familyAspect
Indicates a relationship where one entity is characterized by a particular familial role, status, or aspect in relation to another entity.
-
D.
familyType
Indicates the specific familial relationship or category that characterizes how the related entities are connected as family.
-
E.
familyApplication
Indicates that an application or request is made in the context of a family relationship, typically involving or affecting multiple family members.
- F. None of above. chosen
Provenance (4 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_69e77e8c88f08190858c4c81bd2e1b9a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f643c204508190a43fe0ec5165b01c |
completed | May 2, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f6430975b481909191219ad13ef77e |
completed | May 2, 2026, 6:31 p.m. |
Created at: April 22, 2026, 9:08 a.m.