Triple
T32374311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Express Centurion Card |
E827234
|
entity |
| Predicate | creditLimitType |
P38256
|
FINISHED |
| Object | no preset spending limit |
—
|
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: no preset spending limit | Statement: [American Express Centurion Card, creditLimitType, no preset spending limit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creditLimitType Context triple: [American Express Centurion Card, creditLimitType, no preset spending limit]
-
A.
loanLimitType
Indicates the category or rule that defines how a loan’s maximum allowable amount or terms are limited.
-
B.
guaranteeLimitBasis
Indicates the basis or criteria used to determine the limit of a guarantee in a contractual or financial context.
-
C.
typeOfLimit
chosen
Indicates that one entity specifies the category or kind of limit that applies to another entity.
-
D.
hasTypeOfCredit
Indicates that an entity is associated with or characterized by a specific type or category of credit.
-
E.
monetaryLimit
Indicates a constraint or maximum allowable amount of money associated with an action, transaction, or relationship.
- 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_69f349177ddc8190ab0583f05597056b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c1bb5f248190834161b5a6ba1ece |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:50 a.m.