Triple
T9027568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cell Broadband Engine |
E216085
|
entity |
| Predicate | generalPurposeCore |
P18973
|
FINISHED |
| Object | PowerPC-based core |
—
|
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: PowerPC-based core | Statement: [Cell Broadband Engine, generalPurposeCore, PowerPC-based core]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: generalPurposeCore Context triple: [Cell Broadband Engine, generalPurposeCore, PowerPC-based core]
-
A.
general
Indicates that one entity has a broad, non-specific, or overarching relationship or association with another entity.
-
B.
generalCategory
Indicates that one entity is classified as a broad or overarching category to which the other entity belongs.
-
C.
typicalCoreType
chosen
Indicates that something is a standard or characteristic core type within a given classification or system.
-
D.
hasGeneralPurpose
Indicates that one entity serves as the broad, overarching function, role, or intended use of another entity.
-
E.
commonConcept
Indicates that two or more entities share the same underlying idea, notion, or conceptual meaning.
- 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a7fcb308190af90d6be8700e498 |
completed | April 1, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee132f08190940749c7c522e4c1 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:07 p.m.