Triple
T26176655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zilog |
E654560
|
entity |
| Predicate | Z80CompatibleWith |
P34359
|
FINISHED |
| Object | Intel 8080 software |
—
|
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: Intel 8080 software | Statement: [Zilog, Z80CompatibleWith, Intel 8080 software]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Z80CompatibleWith Context triple: [Zilog, Z80CompatibleWith, Intel 8080 software]
-
A.
isAmigaCompatible
Indicates that something is capable of operating with or supporting the hardware, software, or standards of the Amiga computer platform.
-
B.
supportsApplesoftBASICPrograms
Indicates that an entity is capable of running, interpreting, or otherwise handling programs written in Applesoft BASIC.
-
C.
compatibleFloppyDrive
Indicates that one entity can properly use, read from, or write to floppy disks designed for the other entity.
-
D.
supportsMultitaskingOfDOSPrograms
Indicates that a system or environment is capable of running and managing multiple DOS programs simultaneously.
-
E.
hasHardwareCompatibilityWith
chosen
Indicates that two hardware components or systems can operate together correctly and reliably without conflicts or incompatibilities.
- 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_69ee5b45873c81909499203612d05d07 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60c6c9b808190812dcb252b9844f2 |
completed | May 2, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:38 p.m.