Triple
T14423868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chrome Sync |
E357646
|
entity |
| Predicate | canSync |
P36119
|
FINISHED |
| Object | custom search engines |
—
|
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: custom search engines | Statement: [Chrome Sync, canSync, custom search engines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canSync Context triple: [Chrome Sync, canSync, custom search engines]
-
A.
canSyncVia
chosen
Indicates that one entity is able to synchronize data or state with another entity using a specified method or channel.
-
B.
canBeShared
Indicates that something is capable of being distributed or accessed by multiple parties.
-
C.
dataSyncedTo
Indicates that a set of data has been successfully synchronized from one system or location to another, reflecting the same state or contents.
-
D.
canEnable
Indicates that one entity has the capability or authority to activate, turn on, or make another entity or function operational.
-
E.
canUse
Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
- 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.