Triple
T26333621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zilog Z8000 |
E662458
|
entity |
| Predicate | supportsBlockMoveInstructions |
P196773
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Zilog Z8000, supportsBlockMoveInstructions, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsBlockMoveInstructions Context triple: [Zilog Z8000, supportsBlockMoveInstructions, true]
-
A.
supportsBlock
Indicates that one entity provides structural or functional backing that upholds or stabilizes another entity or block.
-
B.
supportsBlockBasedCoding
Indicates that an entity provides or enables functionality for creating programs using a block-based visual coding interface.
-
C.
supportsBlockStorage
Indicates that one entity provides or is compatible with block-level storage capabilities for another entity.
-
D.
supportsROMBlocks
Indicates that one entity provides compatibility with or the capability to use ROM (Read-Only Memory) blocks associated with another entity.
-
E.
supportsMigrationOf
Indicates that one entity enables, facilitates, or is compatible with the migration or transfer of another entity from one environment, system, or context to another.
- 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_69fe68a4b67881909ca1d9f276f922e0 |
completed | May 8, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69fe680234c88190b01f953987b74972 |
completed | May 8, 2026, 10:47 p.m. |
| PDg | Predicate description generation | batch_69fe68a385f48190b942700e3eddc9b6 |
completed | May 8, 2026, 10:50 p.m. |
Created at: April 26, 2026, 10:35 p.m.