Triple
T29372164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OPM |
E744881
|
entity |
| Predicate | controlClockInput |
P83118
|
FINISHED |
| Object | external clock required |
—
|
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: external clock required | Statement: [OPM, controlClockInput, external clock required]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlClockInput Context triple: [OPM, controlClockInput, external clock required]
-
A.
clockInput
chosen
Indicates that one entity serves as a timing or clock signal input that controls or synchronizes the operation of another entity.
-
B.
hasClockInput
Indicates that an entity receives a clock signal from another entity as an input for timing or synchronization purposes.
-
C.
timeToControl
Indicates the amount of time required for an entity to gain or establish control over another entity, process, or situation.
-
D.
clockType
Indicates the type or category of a clock associated with an entity (e.g., analog, digital, system clock, etc.).
-
E.
clockGeneration
Indicates the action or process of producing a timing clock signal used to synchronize or drive other components or operations.
- 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_69f0a79ba954819094597628112c6091 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: April 28, 2026, 2:28 p.m.