Triple
T37085686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsunami |
E918279
|
entity |
| Predicate | cpuFamilySupported |
P34781
|
FINISHED |
| Object | PowerPC 604 |
—
|
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: PowerPC 604 | Statement: [Tsunami, cpuFamilySupported, PowerPC 604]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cpuFamilySupported Context triple: [Tsunami, cpuFamilySupported, PowerPC 604]
-
A.
cpuFamily
Indicates that one CPU belongs to, or is categorized under, a particular CPU family or architecture lineage.
-
B.
firstSupportedCPUFamily
Indicates the earliest CPU family that a system, software, or feature is designed to support or is compatible with.
-
C.
supportsProcessorFamily
chosen
Indicates that one entity (such as hardware or software) is compatible with and can operate using a specified processor family.
-
D.
chipsetFamily
Indicates that one chipset belongs to, or is categorized under, a particular chipset family or series.
-
E.
supportsModelFamily
Indicates that one entity provides compatibility, functionality, or resources necessary for the operation or use of a particular model family.
- 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_69f76e9952b88190a6fe01ba01476520 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.