Triple
T18506194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jetpack CRM |
E452201
|
entity |
| Predicate | dataOwnershipModel |
P21682
|
FINISHED |
| Object | data stored on user’s own server |
—
|
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: data stored on user’s own server | Statement: [Jetpack CRM, dataOwnershipModel, data stored on user’s own server]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataOwnershipModel Context triple: [Jetpack CRM, dataOwnershipModel, data stored on user’s own server]
-
A.
dataOwner
Indicates that one entity has ownership, control, or primary responsibility over a particular set of data associated with another entity.
-
B.
dataAccessibleTo
Indicates that certain data can be reached, retrieved, or used by a specified entity or system.
-
C.
dataPolicy
Indicates that one entity defines or governs how data related to another entity is collected, used, stored, or shared.
-
D.
dataSegregation
Indicates that data is kept separate or partitioned so that information from one group, context, or user is not mixed or accessible with that of another.
-
E.
ownershipModel
chosen
Indicates the type or structure of ownership relationship that governs how control, rights, or shares are held between entities.
- 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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5334266708190b59aca3a2218c095 |
completed | April 19, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69e469dbf5208190b6fc49e02a087f54 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:36 a.m.