Triple
T14423844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chrome Sync |
E357646
|
entity |
| Predicate | synchronizesAcross |
P25707
|
FINISHED |
| Object | multiple devices |
—
|
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: multiple devices | Statement: [Chrome Sync, synchronizesAcross, multiple devices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: synchronizesAcross Context triple: [Chrome Sync, synchronizesAcross, multiple devices]
-
A.
synchronizesWith
chosen
Indicates that two or more entities coordinate their states or activities so that they occur in step or remain temporally consistent with each other.
-
B.
synchronizationBoundary
Indicates a point or condition at which concurrent or distributed processes must align or coordinate their states or actions to maintain consistency.
-
C.
synchronizationTrigger
Indicates that one process, event, or condition initiates or controls the timing of another so they occur in a coordinated or synchronized manner.
-
D.
syncScope
Indicates that two or more processes, threads, or operations are coordinated to occur within the same synchronization context or boundary.
-
E.
appliesAcross
Indicates that a condition, rule, or property holds uniformly over multiple items, cases, or contexts.
- 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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91123f848190ba3fb18a76c2d24c |
completed | April 14, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69de5c30467881908e770e3940295641 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:18 a.m.