Triple
T11705416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minecoins |
E278224
|
entity |
| Predicate | expires |
P47854
|
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, expires, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expires Context triple: [Minecoins, expires, false]
-
A.
decayDate
Indicates the date on which something ceases to be valid, effective, or usable (i.e., when it expires or decays).
-
B.
canExpire
chosen
Indicates that the subject has the property or status of being able to end, lapse, or become invalid after a certain time or condition is met.
-
C.
usedUntil
Indicates that something remained in use or operation up to a specified time or event, after which it was no longer used.
-
D.
expirationPolicy
Indicates the rules or conditions under which something becomes invalid, unusable, or no longer in effect after a certain time or event.
-
E.
consequenceOfExpiry
Indicates that something occurs as a direct result of an expiry event or the state of having expired.
- 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_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. |
Created at: April 8, 2026, 9:40 p.m.