Triple
T11705414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minecoins |
E278224
|
entity |
| Predicate | transferableBetweenDevices |
P90522
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Minecoins, transferableBetweenDevices, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transferableBetweenDevices Context triple: [Minecoins, transferableBetweenDevices, true]
-
A.
transferBetween
Indicates a movement or handover of something from one entity to another, typically changing its location, ownership, or control between them.
-
B.
canBeAirDropped
Indicates that an item or entity is suitable to be delivered or deployed by being dropped from an aircraft.
-
C.
transferPolicy
Indicates a rule or set of conditions governing when and how something may be transferred from one party or location to another.
-
D.
transferType
Indicates the specific method or category of how something is transferred from one entity to another.
-
E.
transferable
chosen
Indicates that a right, property, or obligation can be legally or practically passed from one entity to another.
- 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.