Triple
T34541643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OsmoTRX |
E886820
|
entity |
| Predicate | supportsClockSource |
P82803
|
FINISHED |
| Object | external reference clock |
—
|
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 reference clock | Statement: [OsmoTRX, supportsClockSource, external reference clock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsClockSource Context triple: [OsmoTRX, supportsClockSource, external reference clock]
-
A.
hasClock
Indicates that one entity possesses, contains, or is equipped with a clock.
-
B.
usesClockControl
Indicates that one entity employs clock-based control mechanisms to regulate or coordinate the operation or timing of another entity or process.
-
C.
hasClockInput
chosen
Indicates that an entity receives a clock signal from another entity as an input for timing or synchronization purposes.
-
D.
usesClockSystem
Indicates that one entity employs or operates according to the clock or timekeeping system defined or provided by another entity.
-
E.
hasClockMaker
Indicates that an entity has, is associated with, or was created/maintained by a specific clock maker.
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2:02 a.m.