Triple
T27663351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Config Sync |
E697173
|
entity |
| Predicate | syncDirection |
P104008
|
FINISHED |
| Object | one-way from source of truth to clusters |
—
|
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: one-way from source of truth to clusters | Statement: [Config Sync, syncDirection, one-way from source of truth to clusters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: syncDirection Context triple: [Config Sync, syncDirection, one-way from source of truth to clusters]
-
A.
synchronizationDirection
chosen
Indicates the direction in which data or state is synchronized between related entities (e.g., one-way or bidirectional).
-
B.
connectionDirection
Indicates the directional flow or orientation of a connection from one entity to another.
-
C.
updateDirection
Indicates changing or setting the current direction or orientation of an entity in response to some input or condition.
-
D.
synchronizationType
Indicates the specific manner or mode in which two or more processes, systems, or events are coordinated to operate in temporal or state alignment.
-
E.
transmissionDirection
Indicates the direction in which something is transmitted or passed from one entity to another.
- 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f634a28ab081908e57cd7e6a15703a |
completed | May 2, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:37 p.m.