Triple
T25436409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | x87 FPU |
E637383
|
entity |
| Predicate | previouslyImplementedAs |
P339
|
FINISHED |
| Object | separate coprocessor chip |
—
|
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: separate coprocessor chip | Statement: [x87 FPU, previouslyImplementedAs, separate coprocessor chip]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previouslyImplementedAs Context triple: [x87 FPU, previouslyImplementedAs, separate coprocessor chip]
-
A.
historicallyImplementedAs
chosen
Indicates that one entity was used or realized as another entity in the past, even if that is no longer the case.
-
B.
firstImplementedBy
Indicates that the subject was initially realized, executed, or put into practice by the specified agent or entity.
-
C.
historicallyImplementedIn
Indicates that an action, practice, or system was carried out or put into effect in a particular place or context during a past historical period.
-
D.
previouslySupported
Indicates that an entity provided support to another entity at some time in the past, but not necessarily in the present.
-
E.
previouslyDefinedIn
Indicates that something has been defined or introduced earlier in time or in a prior context relative to the current reference point.
- 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_69e75db6c97081908178383fa632b193 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 21, 2026, 1:59 p.m.