Triple
T33163585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motorola 6802 |
E848814
|
entity |
| Predicate | hasAccumulator |
P183533
|
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: [Motorola 6802, hasAccumulator, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAccumulator Context triple: [Motorola 6802, hasAccumulator, true]
-
A.
hasCollector
Indicates that an entity is associated with, or owned/curated by, a specific collector.
-
B.
hasTotalisator
Indicates that an entity is associated with or equipped with a totalisator (a system for registering and calculating bets or totals).
-
C.
hasAccelerator
Indicates that one entity possesses or is equipped with an accelerator device or mechanism used to increase speed or energy.
-
D.
hasIncrement
Indicates that one value or state increases by a specified step or amount relative to another.
-
E.
hasAssembler
Indicates that one entity is responsible for assembling, putting together, or constructing another entity.
- 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_69f3495be8808190bbf427733df08aad |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7a01efcc08190bba489a9099b8684 |
completed | May 3, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
| PDg | Predicate description generation | batch_69f79f477c4c8190a35cb6d87b1dcbd1 |
completed | May 3, 2026, 7:17 p.m. |
Created at: May 1, 2026, 1:28 a.m.