Triple
T31583587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Data General AViiON |
E805888
|
entity |
| Predicate | earlierModelsUsed |
P48489
|
FINISHED |
| Object | Motorola 88000 |
—
|
NE NERFINISHED |
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 88000 | Statement: [Data General AViiON, earlierModelsUsed, Motorola 88000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlierModelsUsed Context triple: [Data General AViiON, earlierModelsUsed, Motorola 88000]
-
A.
isEarlyModelOf
Indicates that one entity represents an earlier or initial version, design, or form of another, more developed entity.
-
B.
formerlyUsedBy
chosen
Indicates that an entity was used by another entity in the past but is no longer in use by that entity.
-
C.
replacedEarlierModel
Indicates that one entity has taken the place of another entity that existed or was in use previously.
-
D.
previouslySupportedHardware
Indicates that the subject hardware was supported in the past but is no longer currently supported.
-
E.
emissionsStandardEarlyModels
Indicates that earlier versions or models comply with a specified emissions standard or regulation.
- 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_69f348d3a86c8190a3e5e539a4dd125f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 30, 2026, 10:24 p.m.