Triple
T33057424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MICKEY 2.0 |
E845878
|
entity |
| Predicate | clockingMechanism |
P83118
|
FINISHED |
| Object | mutual clock control between registers |
—
|
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: mutual clock control between registers | Statement: [MICKEY 2.0, clockingMechanism, mutual clock control between registers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clockingMechanism Context triple: [MICKEY 2.0, clockingMechanism, mutual clock control between registers]
-
A.
clockMechanism
Indicates that one entity functions as the internal mechanism or movement that drives the operation of a clock.
-
B.
clockMechanismOrigin
Indicates that one entity is the source, creator, or originating context of a particular clock mechanism associated with another entity.
-
C.
clockMechanismDesigner
Indicates that one entity is the designer or creator of the mechanism of a clock associated with another entity.
-
D.
clockMechanismEngineer
Indicates that one entity is an engineer who designs, builds, or maintains clock mechanisms for another entity or context.
-
E.
clockInput
chosen
Indicates that one entity serves as a timing or clock signal input that controls or synchronizes the operation of another entity.
- 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_69f3495333b8819095e9af56855b9061 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:25 a.m.