Triple
T25177350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Socket M |
E630483
|
entity |
| Predicate | compatibleProcessorFamily |
P34781
|
FINISHED |
| Object | Intel Yonah |
E630482
|
NE 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: Intel Yonah | Statement: [Socket M, compatibleProcessorFamily, Intel Yonah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compatibleProcessorFamily Context triple: [Socket M, compatibleProcessorFamily, Intel Yonah]
-
A.
supportsProcessorFamily
chosen
Indicates that one entity (such as hardware or software) is compatible with and can operate using a specified processor family.
-
B.
cpuFamily
Indicates that one CPU belongs to, or is categorized under, a particular CPU family or architecture lineage.
-
C.
hasHardwareCompatibilityWith
Indicates that two hardware components or systems can operate together correctly and reliably without conflicts or incompatibilities.
-
D.
predecessorCpuArchitecture
Indicates that one CPU architecture directly precedes another in an evolutionary or historical development sequence.
-
E.
compatibleSign
Indicates that two entities are considered astrologically harmonious or well-matched based on their zodiac signs.
- F. None of above.
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_69e75a88fdf081908e47ae6e195c14e1 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a1075c5b7cc8190b2c9c6fea539fd28 |
completed | May 22, 2026, 3:27 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
Created at: April 21, 2026, 12:34 p.m.