Triple
T30663269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aeroplan points |
E780588
|
entity |
| Predicate | transferableFrom |
P44347
|
FINISHED |
| Object | select bank rewards programs |
—
|
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: select bank rewards programs | Statement: [Aeroplan points, transferableFrom, select bank rewards programs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transferableFrom Context triple: [Aeroplan points, transferableFrom, select bank rewards programs]
-
A.
transferFrom
chosen
Indicates a transfer action where something is moved from a specified source entity to another entity or account.
-
B.
transferRole
Indicates that one entity passes a role, position, or set of responsibilities to another entity.
-
C.
transferable
Indicates that a right, property, or obligation can be legally or practically passed from one entity to another.
-
D.
allowsTransferTo
Indicates that one entity permits or enables the transfer of something (such as rights, funds, or data) to another specified entity.
-
E.
transferAfter
Indicates that one entity transfers something to another entity only after a specified event or condition has occurred.
- 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_69f224a6d10481909290be1a00fc83b3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fde49a084081909d99b1e0258169d5 |
completed | May 8, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69fde1d04bd881909a46ecbbf18dfe59 |
completed | May 8, 2026, 1:14 p.m. |
Created at: April 29, 2026, 8:31 p.m.