Triple
T35068956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Betclic |
E1011812
|
entity |
| Predicate | acceptsCurrency |
P85722
|
FINISHED |
| Object | euro |
—
|
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: euro | Statement: [Betclic, acceptsCurrency, euro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acceptsCurrency Context triple: [Betclic, acceptsCurrency, euro]
-
A.
usesCurrency
Indicates that one entity conducts its financial transactions or values using the monetary unit represented by the other entity.
-
B.
currencyOnboard
chosen
Indicates that a particular currency has been enabled, registered, or made available for use within a given system or context.
-
C.
servesCurrencyUnion
Indicates that an entity functions as the central authority or administrative body for a specific currency union.
-
D.
usesSupplementaryCurrency
Indicates that an entity employs an additional, non-primary currency alongside its main currency for transactions or value exchange.
-
E.
legalTenderSupported
Indicates that a given currency or payment method is officially recognized and accepted as legal tender within a specified jurisdiction or context.
- 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_69f76dd193108190af2528186f25b72a |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7861a3eb481909f9bd86edbbc3947 |
completed | May 3, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.