Triple
T14396396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zopim |
E356958
|
entity |
| Predicate | typicalIntegration |
P8841
|
FINISHED |
| Object | embedded on customer websites |
—
|
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: embedded on customer websites | Statement: [Zopim, typicalIntegration, embedded on customer websites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalIntegration Context triple: [Zopim, typicalIntegration, embedded on customer websites]
-
A.
typeOfIntegration
chosen
Indicates the specific kind or category of integration that exists or is applied between systems, components, or processes.
-
B.
integrates
Indicates that one entity combines or brings together another entity or set of entities into a unified, functioning whole.
-
C.
integratorType
Indicates the specific kind or category of integrator associated with or used in relation to an entity.
-
D.
integratesOn
Indicates that one entity is designed to work seamlessly within, or be combined functionally with, another entity or platform.
-
E.
typicalInterface
Indicates that one entity serves as the standard or commonly used interface through which another entity is accessed or interacted with.
- 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_69d827927c988190ad98bb0360981783 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de90826f908190b3969af9b7cf922f |
completed | April 14, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_69de2aa024c48190805df6a9d63deb10 |
completed | April 14, 2026, 11:53 a.m. |
Created at: April 10, 2026, 1:17 a.m.