Triple
T32374295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Express Centurion Card |
E827234
|
entity |
| Predicate | feeLevel |
P173986
|
FINISHED |
| Object | very high annual fee |
—
|
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: very high annual fee | Statement: [American Express Centurion Card, feeLevel, very high annual fee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: feeLevel Context triple: [American Express Centurion Card, feeLevel, very high annual fee]
-
A.
feeUnit
Indicates the unit of measurement or currency in which a fee amount is expressed.
-
B.
feeType
Indicates the specific category or classification of a fee associated with a transaction, service, or obligation.
-
C.
feeStatus
Indicates the current state or condition of fees associated with an entity, such as whether they are due, paid, waived, or overdue.
-
D.
greenFeeLevel
Indicates the pricing tier or cost level associated with a green fee for using a golf course.
-
E.
feePolicy
Indicates the rules or conditions that determine how fees are calculated, applied, or charged in a given context.
- 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_69f349177ddc8190ab0583f05597056b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c12eb9b88190b6d1a371081717b0 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
| PDg | Predicate description generation | batch_69f6bb344bb48190a8089f29c0063ded |
completed | May 3, 2026, 3:04 a.m. |
Created at: May 1, 2026, 12:50 a.m.