Triple
T322239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PTP |
E6437
|
entity |
| Predicate | synchronizes |
P2194
|
FINISHED |
| Object | slave clocks to master 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: slave clocks to master clock | Statement: [PTP, synchronizes, slave clocks to master clock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: synchronizes Context triple: [PTP, synchronizes, slave clocks to master clock]
-
A.
ensures
chosen
Indicates that one entity guarantees or makes certain that a particular condition, outcome, or state holds for another entity or situation.
-
B.
coordinatedWith
Indicates that two or more entities have worked together in an organized, cooperative manner toward a shared task, goal, or activity.
-
C.
suspension
Indicates the temporary removal or halting of a privilege, activity, or status for an entity, often as a consequence or precaution.
-
D.
coincidesWith
Indicates that two entities occupy the same position, time, or state such that they exactly overlap or occur together.
-
E.
receives
Indicates that one entity is the recipient of something (such as an object, message, or action) from 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_69a2e7933d6c8190bb2592ad13286ef2 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea81a1e88190b3496070eb3d85f5 |
completed | Feb. 28, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69a2e948048c819098ba4de9261ef2ef |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.