Triple
T23804454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JMB Sapphire |
E589663
|
entity |
| Predicate | cardTypeAvailable |
P5430
|
FINISHED |
| Object | JAL Global Club membership card (when combined with JGC) |
—
|
NE NERFINISHED |
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: JAL Global Club membership card (when combined with JGC) | Statement: [JMB Sapphire, cardTypeAvailable, JAL Global Club membership card (when combined with JGC)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cardTypeAvailable Context triple: [JMB Sapphire, cardTypeAvailable, JAL Global Club membership card (when combined with JGC)]
-
A.
cardType
chosen
Indicates the classification or category assigned to a card within a given system or context.
-
B.
cardEligibility
Indicates whether an entity qualifies for or is allowed to receive a particular card under specified criteria.
-
C.
cardTypeAccess
Indicates that access or permissions are determined or constrained based on the type of card involved.
-
D.
cardFormat
Indicates the specific layout or structural style in which a card or card-like item is presented or encoded.
-
E.
hasCreditCardVariant
Indicates that one credit card is a specific version, type, or variation of another credit card.
- 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_69e25d19fecc8190a5cf39bbb18d5d7f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c750048c8190899ff611df35b361 |
completed | April 29, 2026, 8:54 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:55 p.m.