Triple
T26333593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zilog Z8000 |
E662458
|
entity |
| Predicate | registersCanBeGrouped |
P74342
|
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, registersCanBeGrouped, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: registersCanBeGrouped Context triple: [Zilog Z8000, registersCanBeGrouped, true]
-
A.
areSometimesGroupedWith
Indicates that two or more entities are occasionally but not consistently classified, treated, or considered together as part of the same group.
-
B.
groupedInto
chosen
Indicates that multiple entities are collected or organized together as members of a common group or category.
-
C.
movementGrouping
Indicates that multiple movements or motion events are treated as a single grouped or coordinated unit within a larger action or process.
-
D.
groupingRule
Indicates a rule or criterion that defines how multiple entities are grouped or clustered together based on shared characteristics or conditions.
-
E.
allyGroup
Indicates that two or more entities belong to the same allied group or faction, cooperating or aligned in purpose or interests.
- 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_69ee812f32748190871d970c4e2a8ddf |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620debeb48190b7db395fb86cf8d9 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 26, 2026, 10:35 p.m.