Triple
T16598090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ath.ena Card |
E403260
|
entity |
| Predicate | personalizedCardSupports |
P123462
|
FINISHED |
| Object | online top-up |
—
|
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 top-up | Statement: [Ath.ena Card, personalizedCardSupports, online top-up]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: personalizedCardSupports Context triple: [Ath.ena Card, personalizedCardSupports, online top-up]
-
A.
cardEligibility
Indicates whether an entity qualifies for or is allowed to receive a particular card under specified criteria.
-
B.
hadCoBrandedCreditCardsWith
Indicates that two entities jointly issued or partnered on one or more co-branded credit card products.
-
C.
legalCardsFrom
Indicates that the referenced cards are permitted or valid according to the rules or constraints defined by the specified source or authority.
-
D.
containsCard
Indicates that one entity includes or holds a specific card as part of its contents or collection.
-
E.
cardFormat
Indicates the specific layout or structural style in which a card or card-like item is presented or encoded.
- F. None of above. chosen
Provenance (4 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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35d7367308190bf57b4a6a7bd33cc |
completed | April 18, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_69e296a7d9d0819088555bca6c936e79 |
completed | April 17, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69e2d7fb02f481908885a226c2191231 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:16 a.m.