Triple
T4518764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aeroflot Bonus |
E103214
|
entity |
| Predicate | pointEarningMethod |
P35525
|
FINISHED |
| Object | Aeroflot flights |
—
|
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: Aeroflot flights | Statement: [Aeroflot Bonus, pointEarningMethod, Aeroflot flights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pointEarningMethod Context triple: [Aeroflot Bonus, pointEarningMethod, Aeroflot flights]
-
A.
loyaltyProgramEarnings
Indicates the amount or details of rewards or benefits a participant accrues within a loyalty or rewards program.
-
B.
mileEarningUnit
Indicates the unit or basis (e.g., per mile, per dollar) used to calculate or award mileage or points in a mileage-earning relationship.
-
C.
earnsRewardsCurrency
chosen
Indicates that an entity receives or accumulates a specified rewards currency as a result of some action, status, or relationship.
-
D.
powerCollectionMethod
Indicates the method or process by which power is collected, harvested, or obtained in a given context.
-
E.
earnsMorePointsThan
Indicates that one entity receives a greater number of points than another entity in a given context or comparison.
- 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_69bd43dba59881908cf59b31df8c7ae1 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd57465a10819086866e29f7a6eb02 |
completed | March 20, 2026, 2:18 p.m. |
| PD | Predicate disambiguation | batch_69bd521abea48190b3e758a1f98dd55e |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:02 p.m.