Triple
T3811394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macintosh II |
E93142
|
entity |
| Predicate | coprocessorType |
P6678
|
FINISHED |
| Object | floating-point unit |
—
|
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: floating-point unit | Statement: [Macintosh II, coprocessorType, floating-point unit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coprocessorType Context triple: [Macintosh II, coprocessorType, floating-point unit]
-
A.
processType
Indicates the specific kind or category of process that an entity or activity belongs to.
-
B.
typeOfCluster
Indicates that one entity is classified as a specific kind or category of cluster in relation to another entity.
-
C.
componentType
chosen
Indicates that one entity specifies or classifies the kind or category of component that another entity represents or uses.
-
D.
brickProcessorType
Indicates the specific kind or category of processor associated with a given brick.
-
E.
builtInProcessor
Indicates that one entity serves as an internal or integrated processing unit within another entity.
- 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_69aed96a60088190ab1df8390fffc935 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aef1515c688190a38332aedeed8a76 |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee7482d708190a3ec74745b102a4c |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:16 p.m.