Triple
T17381912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flying Club miles |
E422588
|
entity |
| Predicate | nonCashEquivalent |
P7014
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Flying Club miles, nonCashEquivalent, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nonCashEquivalent Context triple: [Flying Club miles, nonCashEquivalent, yes]
-
A.
notPhysicalCash
Indicates that the transaction, payment, or value transfer does not involve tangible paper money or coins, but instead uses non-cash forms such as digital, electronic, or other non-physical means.
-
B.
nonMonetary
Indicates that the relationship or transaction occurs without the exchange or involvement of money or financial compensation.
-
C.
nonTransferable
Indicates that a right, asset, or privilege cannot be legally or contractually transferred from one party to another.
-
D.
notRedeemableFor
chosen
Indicates that something cannot be exchanged, converted, or used to obtain another specified item, service, or benefit.
-
E.
nonVolatile
Indicates that the associated entity or state does not change, disappear, or lose its value when power is removed or over time.
- 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a86d8cc81909281b22f5da87d70 |
completed | April 19, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69e3b02ac8688190a7182f1b2151d721 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:45 a.m.