Triple
T36908045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Test Access Port |
E912830
|
entity |
| Predicate | operatesWithClock |
P82803
|
FINISHED |
| Object | TCK |
—
|
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: TCK | Statement: [Test Access Port, operatesWithClock, TCK]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesWithClock Context triple: [Test Access Port, operatesWithClock, TCK]
-
A.
usesClockSystem
Indicates that one entity employs or operates according to the clock or timekeeping system defined or provided by another entity.
-
B.
hasClock
Indicates that one entity possesses, contains, or is equipped with a clock.
-
C.
usesClockControl
Indicates that one entity employs clock-based control mechanisms to regulate or coordinate the operation or timing of another entity or process.
-
D.
hasClockInput
chosen
Indicates that an entity receives a clock signal from another entity as an input for timing or synchronization purposes.
-
E.
operatesAtTime
Indicates that an action, process, or system is functioning or active during a specified time or time interval.
- 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_69f76e879768819085c2fb31a6a5b44b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a01ca0db6f08190bed479584114e63d |
completed | May 11, 2026, 12:22 p.m. |
| PD | Predicate disambiguation | batch_6a01c96ff4a08190a4fbf0cebbda95b4 |
completed | May 11, 2026, 12:20 p.m. |
Created at: May 3, 2026, 4:13 p.m.