Triple
T37403720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Latitude 9000 series |
E929067
|
entity |
| Predicate | typicalProcessorClass |
P186412
|
FINISHED |
| Object | high-performance mobile processors |
—
|
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: high-performance mobile processors | Statement: [Latitude 9000 series, typicalProcessorClass, high-performance mobile processors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalProcessorClass Context triple: [Latitude 9000 series, typicalProcessorClass, high-performance mobile processors]
-
A.
mainProcessorType
chosen
Indicates the type or category of processor that serves as the primary or central processing unit for a given system or device.
-
B.
introducedByProcessorFamily
Indicates that one entity was brought into existence, use, or context by a specific processor family.
-
C.
relatedProcessor
Indicates that one processor has a defined relationship or association with another processor, such as being linked, paired, or otherwise connected in processing tasks.
-
D.
builtInProcessor
Indicates that one entity serves as an internal or integrated processing unit within another entity.
-
E.
typicalProcess
Indicates that the related process is characteristic, usual, or commonly occurring for the given entity or context.
- 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_69f76ebbf79c8190b85bbcf3a6be57e4 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:16 p.m.