Triple
T19374692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boursorama |
E484635
|
entity |
| Predicate | customerAccess |
P32027
|
FINISHED |
| Object | online account opening |
—
|
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: online account opening | Statement: [Boursorama, customerAccess, online account opening]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: customerAccess Context triple: [Boursorama, customerAccess, online account opening]
-
A.
serviceUser
Indicates that one entity is a user or consumer of a service provided by another entity.
-
B.
exportCustomer
Indicates initiating the transfer or output of customer-related data from one system or context to another, typically for integration, backup, or reporting purposes.
-
C.
customerGroup
Indicates a relationship in which an entity belongs to, is classified under, or is associated with a particular group of customers.
-
D.
accessStatus
chosen
Indicates the current level or state of permission or availability for accessing a resource or entity.
-
E.
customerType
Indicates the classification or category assigned to a customer based on their characteristics, status, or relationship with a business.
- 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_69d8e8d460d88190abf0591c5c9d2b0c |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61a5acc4481908fecfb57af16d037 |
completed | April 20, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_69e4fd54f8e48190956e73dd8969164a |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:35 p.m.