Triple
T32563156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frontier Miles |
E832280
|
entity |
| Predicate | expirationCanBeExtendedBy |
P174600
|
FINISHED |
| Object | earning activity |
—
|
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: earning activity | Statement: [Frontier Miles, expirationCanBeExtendedBy, earning activity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expirationCanBeExtendedBy Context triple: [Frontier Miles, expirationCanBeExtendedBy, earning activity]
-
A.
leaseExtendedUntil
Indicates that an existing lease agreement has been prolonged so that its validity now continues up to a specified end date.
-
B.
lifetimeExtensionDecision
Indicates a decision has been made to extend the operational lifetime or validity period of an entity beyond its originally planned end date.
-
C.
extensionEffectiveDate
Indicates the date on which an extension to an existing agreement, term, or condition becomes effective.
-
D.
extendedAuthorityTo
Indicates that one entity has granted or delegated its decision-making power or control to another entity.
-
E.
canExpire
Indicates that the subject has the property or status of being able to end, lapse, or become invalid after a certain time or condition is met.
- 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_69f34926b9848190ace47d2dd0a0de7c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c60b4a508190914cc090b93dcbe1 |
completed | May 3, 2026, 3:50 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c1b666188190ac43c3011a7df048 |
completed | May 3, 2026, 3:32 a.m. |
Created at: May 1, 2026, 1:03 a.m.