Triple
T12046052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macintosh Performa 200 |
E286789
|
entity |
| Predicate | fpu |
P86810
|
FINISHED |
| Object | optional Motorola 68882 |
—
|
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: optional Motorola 68882 | Statement: [Macintosh Performa 200, fpu, optional Motorola 68882]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fpu Context triple: [Macintosh Performa 200, fpu, optional Motorola 68882]
-
A.
FPU
chosen
Indicates that one entity functions as or contains a floating-point unit responsible for performing arithmetic operations on non-integer (floating-point) numbers for another entity or within a system.
-
B.
compatibleFPU
Indicates that two processing units or components can interoperate correctly and reliably with respect to floating-point operations.
-
C.
numberOfFloatingPointUnits
Indicates the quantity of floating-point processing units associated with or contained in an entity.
-
D.
floatingPointRegisterCount
Indicates the number of floating-point registers associated with an entity (such as a processor or execution context).
-
E.
floatingPointPerformance
Indicates the level of computational capability or efficiency an entity has when performing floating-point arithmetic operations.
- 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_69d6ab4780948190bdb9f7620c2ac27e |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902bac9e08190aa1a99c835f29542 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:47 p.m.