Triple
T26333597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zilog Z8000 |
E662458
|
entity |
| Predicate | supportsSeparateIOMode |
P196535
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Zilog Z8000, supportsSeparateIOMode, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsSeparateIOMode Context triple: [Zilog Z8000, supportsSeparateIOMode, false]
-
A.
supportsMultipleStreams
Indicates that the subject is capable of handling or maintaining more than one data or communication stream at the same time.
-
B.
usesSeparateChannelFor
Indicates that one entity communicates with or accesses another entity through a distinct, dedicated channel separate from other communications or interactions.
-
C.
supportsSeparateCompilation
Indicates that one element enables or allows another to be compiled independently from the rest of the system or program.
-
D.
supportsMultipleTerminals
Indicates that an entity is capable of handling or operating with more than one terminal or endpoint simultaneously.
-
E.
supportsSeparateAccounts
Indicates that one entity enables or allows the use or management of distinct, individually maintained accounts rather than a single shared account.
- F. None of above. chosen
Provenance (4 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_69ee812f32748190871d970c4e2a8ddf |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69fe5c1a502081909d4024e514309c8e |
completed | May 8, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69fe5a9df21c819087153f5d0bcaa987 |
completed | May 8, 2026, 9:50 p.m. |
| PDg | Predicate description generation | batch_69fe5c196f4081908f150d4cd6c528fa |
completed | May 8, 2026, 9:56 p.m. |
Created at: April 26, 2026, 10:35 p.m.