Triple
T1624186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leonardo Hotels |
E35099
|
entity |
| Predicate | acceptsPaymentMethod |
P5428
|
FINISHED |
| Object | credit cards |
—
|
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: credit cards | Statement: [Leonardo Hotels, acceptsPaymentMethod, credit cards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acceptsPaymentMethod Context triple: [Leonardo Hotels, acceptsPaymentMethod, credit cards]
-
A.
supportsTapToPay
Indicates that an entity enables or is compatible with tap-to-pay (contactless) payment functionality.
-
B.
paymentMethod
chosen
Indicates the means or instrument through which a payment is made in a transaction.
-
C.
paymentEnvironment
Indicates the context or setting in which a payment is initiated, processed, or completed (such as online, in-store, or in-app).
-
D.
supportsOpenLoopPayments
Indicates that an entity enables or is compatible with open-loop payment methods, where transactions are processed over general-purpose payment networks rather than a closed, proprietary system.
-
E.
paymentSystem
Indicates a relationship where one entity functions as a mechanism or platform through which another entity makes or processes payments.
- 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_69a886023194819080a3fccd6e325d0e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf4a0ef748190ae52b9656474c0ef |
completed | March 6, 2026, 3:37 p.m. |
| PD | Predicate disambiguation | batch_69a907c731808190a1d998155041b3c1 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.