Triple
T9855652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Express Green Card |
E239576
|
entity |
| Predicate | hasPhysicalCard |
P90361
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [American Express Green Card, hasPhysicalCard, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPhysicalCard Context triple: [American Express Green Card, hasPhysicalCard, yes]
-
A.
hasPin
Indicates that one entity possesses, includes, or is equipped with a specific pin (such as a connector pin, security PIN, or fastening pin).
-
B.
hasCardNumber
Indicates that an entity is associated with, or assigned, a specific card number.
-
C.
hasPINCode
Indicates that an entity is associated with or assigned a specific personal identification number (PIN) code.
-
D.
notPhysicalCash
Indicates that the transaction, payment, or value transfer does not involve tangible paper money or coins, but instead uses non-cash forms such as digital, electronic, or other non-physical means.
-
E.
hasDigitalWallet
Indicates that an entity possesses or is associated with a digital wallet for storing and managing digital payment instruments or assets.
- 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_69ca84e6493081909cf58c8d42ea856b |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb39719288190adf45e7c029edd51 |
completed | April 2, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69cd03e73ec48190bc30fa781978d817 |
completed | April 1, 2026, 11:39 a.m. |
| PDg | Predicate description generation | batch_69cd06ace53081909b5f81f382f6591e |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:35 p.m.