Triple
T32187753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daily Cash |
E822151
|
entity |
| Predicate | feeForEarning |
P25908
|
FINISHED |
| Object | no additional 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: no additional fee | Statement: [Daily Cash, feeForEarning, no additional fee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: feeForEarning Context triple: [Daily Cash, feeForEarning, no additional fee]
-
A.
feeUnit
Indicates the unit of measurement or currency in which a fee amount is expressed.
-
B.
feeComponents
Indicates that a fee is composed of one or more sub-fees or cost elements that together make up the total charge.
-
C.
feePolicy
chosen
Indicates the rules or conditions that determine how fees are calculated, applied, or charged in a given context.
-
D.
feeType
Indicates the specific category or classification of a fee associated with a transaction, service, or obligation.
-
E.
chargesFeeFor
Indicates that one entity requires payment of a fee from another entity in exchange for a specific service, product, or privilege.
- 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_69f3490819cc81909bae1f8ce99423c5 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6babc938c8190a233c3a8b5254802 |
completed | May 3, 2026, 3:02 a.m. |
| PD | Predicate disambiguation | batch_69f6b3aa892481908d29283a074e6722 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:35 a.m.