Triple
T23183040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Afterpay Limited |
E579510
|
entity |
| Predicate | lateFeePolicy |
P25908
|
FINISHED |
| Object | late fees for missed payments |
—
|
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: late fees for missed payments | Statement: [Afterpay Limited, lateFeePolicy, late fees for missed payments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lateFeePolicy Context triple: [Afterpay Limited, lateFeePolicy, late fees for missed payments]
-
A.
feePolicy
chosen
Indicates the rules or conditions that determine how fees are calculated, applied, or charged in a given context.
-
B.
farePolicyType
Indicates the type or category of fare policy that governs how prices, rules, or conditions are applied.
-
C.
farePolicyAspect
Indicates a specific rule, condition, or feature that characterizes some aspect of a fare policy.
-
D.
feeStatus
Indicates the current state or condition of fees associated with an entity, such as whether they are due, paid, waived, or overdue.
-
E.
penaltyAppliesTo
Indicates that a specific penalty is imposed on, or is relevant to, a particular entity or situation.
- 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_69e245ff8000819090d12008805315b7 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18f705c14819082c8580a03ed6286 |
completed | April 29, 2026, 4:56 a.m. |
| PD | Predicate disambiguation | batch_69ef8a041c0081909afb670d17a5aaba |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:05 p.m.