Triple
T29247015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zorro II |
E741465
|
entity |
| Predicate | typicalClockSource |
—
|
ONPD |
| Object | system 68000 CPU clock |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalClockSource Context triple: [Zorro II, typicalClockSource, system 68000 CPU clock]
-
A.
clockGeneration
Indicates the action or process of producing a timing clock signal used to synchronize or drive other components or operations.
-
B.
usesClockSystem
Indicates that one entity employs or operates according to the clock or timekeeping system defined or provided by another entity.
-
C.
hasClockInput
chosen
Indicates that an entity receives a clock signal from another entity as an input for timing or synchronization purposes.
-
D.
usesClockControl
Indicates that one entity employs clock-based control mechanisms to regulate or coordinate the operation or timing of another entity or process.
-
E.
hasClock
Indicates that one entity possesses, contains, or is equipped with a clock.
- F. None of above.
Provenance (2 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_69f0911eba2c8190b07cd2fdf91422c9 |
completed | April 28, 2026, 10:51 a.m. |
| PD | Predicate disambiguation | batch_6a01961bb748819096a941f1b5443908 |
in_progress | May 11, 2026, 8:40 a.m. |
Created at: April 28, 2026, 12:33 p.m.