Triple
T8414142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Artesyn Embedded Technologies |
E198691
|
entity |
| Predicate | continuesProductLinesFrom |
P20918
|
FINISHED |
| Object | Motorola VMEbus systems business |
—
|
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: Motorola VMEbus systems business | Statement: [Artesyn Embedded Technologies, continuesProductLinesFrom, Motorola VMEbus systems business]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuesProductLinesFrom Context triple: [Artesyn Embedded Technologies, continuesProductLinesFrom, Motorola VMEbus systems business]
-
A.
productLineStart
Indicates the point in time or position at which a particular product line begins or is first introduced.
-
B.
belongsToProductLine
Indicates that an item or product is associated with and classified under a specific product line.
-
C.
continuedBy
chosen
Indicates that one entity carries on, extends, or resumes the activity, process, or sequence initiated by another entity.
-
D.
laterProductType
Indicates that one product type occurs or is introduced after another product type in time or sequence.
-
E.
connectedLine
Indicates that two entities are joined by a continuous line or linear connection.
- 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_69ca831201b481909e137936ef99ff11 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb83e328cc8190b3b038005d0bb66f |
completed | March 31, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69cb70d473dc8190af8ea81ee5aa970d |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:06 p.m.