Triple
T14435949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marriott Bonvoy |
E357959
|
entity |
| Predicate | allowsPointTransferTo |
P38153
|
FINISHED |
| Object | various frequent flyer 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: various frequent flyer programs | Statement: [Marriott Bonvoy, allowsPointTransferTo, various frequent flyer programs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsPointTransferTo Context triple: [Marriott Bonvoy, allowsPointTransferTo, various frequent flyer programs]
-
A.
allowsTransferTo
chosen
Indicates that one entity permits or enables the transfer of something (such as rights, funds, or data) to another specified entity.
-
B.
hasTransferOption
Indicates that there exists a way or method for something (e.g., funds, data, ownership, or passengers) to be transferred from one entity or location to another.
-
C.
mayBeTransferredIf
Indicates that something is allowed to be transferred from one party or context to another under certain conditions.
-
D.
hasTransfer
Indicates a relationship where something is moved or conveyed from one entity or location to another.
-
E.
transferBetween
Indicates a movement or handover of something from one entity to another, typically changing its location, ownership, or control between them.
- 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_69d8279402a88190821ffa39ae15bccf |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de9148cf4481909082cc91b2f76218 |
completed | April 14, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69de5c3a02fc819097373f97a260cdeb |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:18 a.m.