Triple
T10524477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Copa ConnectMiles Platinum |
E248261
|
entity |
| Predicate | qualifyingActivityType |
P20949
|
FINISHED |
| Object | flight miles |
—
|
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: flight miles | Statement: [Copa ConnectMiles Platinum, qualifyingActivityType, flight miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: qualifyingActivityType Context triple: [Copa ConnectMiles Platinum, qualifyingActivityType, flight miles]
-
A.
hasActivityType
chosen
Indicates the specific kind or category of activity associated with an entity or event.
-
B.
qualifyingEvent
Indicates that an event meets specific conditions or criteria that make an entity eligible for a particular status, action, or outcome.
-
C.
offersQualificationType
Indicates that an entity provides or makes available a specific type or category of qualification.
-
D.
permittedActivity
Indicates that a particular action or behavior is allowed or authorized within a given context or under specified rules.
-
E.
eligibilityCategory
Indicates the classification or type of eligibility that applies to an entity within a given context.
- 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_69d381c5c7448190bec34bee7ec72bac |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509f4020c8190b78c49da086df757 |
completed | April 7, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_69d4fb94fa10819091f585bab4379c6f |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:29 p.m.