Triple
T37698667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Miles |
E938994
|
entity |
| Predicate | activityToEarn |
P61422
|
FINISHED |
| Object | flying with Airblue |
—
|
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: flying with Airblue | Statement: [Blue Miles, activityToEarn, flying with Airblue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activityToEarn Context triple: [Blue Miles, activityToEarn, flying with Airblue]
-
A.
earnActivity
chosen
Indicates that an entity gains or receives something of value (such as money, points, or rewards) as a result of performing a particular activity.
-
B.
activityType
Indicates the specific kind or category of action or event that an entity is engaged in or associated with.
-
C.
otherActivity
Indicates that an entity is engaged in an activity that is different from a primary, specified, or expected activity.
-
D.
offersActivity
Indicates that one entity provides or makes available a specific activity for another entity to participate in or use.
-
E.
awardedForActivitiesIn
Indicates that an award or recognition is given to an entity specifically because of activities carried out in a particular field, context, or domain.
- 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_69f76eda6ae48190b3111071eeacc038 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: May 3, 2026, 4:18 p.m.