Triple
T17343818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulic Qel-Droma |
E421130
|
entity |
| Predicate | redemptionStatus |
P127116
|
FINISHED |
| Object | redeemed |
—
|
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: redeemed | Statement: [Ulic Qel-Droma, redemptionStatus, redeemed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: redemptionStatus Context triple: [Ulic Qel-Droma, redemptionStatus, redeemed]
-
A.
redemptionType
Indicates the manner or method by which something (such as a benefit, reward, or obligation) can be redeemed or fulfilled.
-
B.
redeemedAs
Indicates that one entity is exchanged, converted, or claimed in return for another specified benefit, value, or status.
-
C.
redeemedBy
Indicates that something (such as a code, voucher, coupon, or offer) has been claimed, exchanged, or converted into its associated benefit or value by a particular entity.
-
D.
redemptionOptions
Indicates the ways or methods by which something (such as points, credits, or vouchers) can be redeemed or exchanged for value.
-
E.
redemptionDependsOn
Indicates that the ability or process of redemption is contingent upon, or determined by, another specified factor or condition.
- F. None of above. chosen
Provenance (4 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_69d889d3adc881909319f1edb8d2a956 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a27a350819086faf12e6bf9f0e2 |
completed | April 19, 2026, 2:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b02662d08190a07d0fb5c04b6f33 |
completed | April 18, 2026, 4:24 p.m. |
| PDg | Predicate description generation | batch_69e3b2a225b08190a50f984caa6513b9 |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:44 a.m.