Triple
T11334473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Power Macintosh 9600 |
E268432
|
entity |
| Predicate | motherboardCodeName |
P43129
|
FINISHED |
| Object | Tsunami |
—
|
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: Tsunami | Statement: [Power Macintosh 9600, motherboardCodeName, Tsunami]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: motherboardCodeName Context triple: [Power Macintosh 9600, motherboardCodeName, Tsunami]
-
A.
chipSetName
Indicates the specific chipset designation or model name associated with a hardware component or device.
-
B.
chipsetBrand
Indicates the brand or manufacturer associated with a device’s chipset.
-
C.
cpuModel
Indicates the specific processor model associated with a given computing device or system.
-
D.
mainBoardName
chosen
Indicates the name or designation assigned to a main board (e.g., primary circuit board or central hardware board) associated with an entity.
-
E.
relatedCodename
Indicates that one entity has an associated or connected codename that is contextually related to it.
- 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9fe5d5881908d786b212a554d8b |
completed | April 9, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69d787afe5a48190b8af1a3e19529641 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:33 p.m.