Triple
T11705415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minecoins |
E278224
|
entity |
| Predicate | refundable |
P101349
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Minecoins, refundable, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refundable Context triple: [Minecoins, refundable, false]
-
A.
refundabilityType
Indicates the specific conditions or category under which something (typically a payment, ticket, or product) can be refunded.
-
B.
refundablePortionName
Indicates the specific name or label assigned to the portion of an amount that is eligible to be refunded.
-
C.
refundForm
Indicates that an entity is a form or process used to request or process a refund for another entity.
-
D.
reversible
Indicates that the relationship or process can proceed in both directions, allowing a return to the original state or configuration.
-
E.
refundPolicy
Indicates the terms and conditions under which payments are returned or compensated after a purchase or transaction.
- 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_69d6aaff2ce88190b4a1e4b341ad5377 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a49c8c38819083d83f5fdec52b7f |
completed | April 10, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69d88a7b30948190b616a9db5c5488d5 |
completed | April 10, 2026, 5:28 a.m. |
| PDg | Predicate description generation | batch_69d89546a8688190b51455b5e12caf91 |
completed | April 10, 2026, 6:14 a.m. |
Created at: April 8, 2026, 9:40 p.m.