Triple
T28079730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Presto |
E709642
|
entity |
| Predicate | supportsOnlineReload |
P84249
|
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: [Presto, supportsOnlineReload, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsOnlineReload Context triple: [Presto, supportsOnlineReload, true]
-
A.
isReloadableOnline
chosen
Indicates that an item, service, or account balance can be replenished or topped up through an online process.
-
B.
allowsAutoReload
Indicates that one entity permits another entity or process to automatically reload or refresh without manual intervention.
-
C.
isReloadable
Indicates that an entity can be loaded again or refreshed, typically after being used, changed, or depleted.
-
D.
supportsOnlineContent
Indicates that one entity provides the infrastructure, functionality, or capability for another entity to host, deliver, or interact with content over the internet.
-
E.
supportsDynamicLoading
Indicates that an entity is capable of loading components or resources at runtime rather than only at startup or compile 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_69ef9b7037f0819095bb90eaccbcaf32 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_6a005e8a2f7c819085bfc6f04b866d87 |
completed | May 10, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_6a005de82ef08190a015b385d1d3443c |
completed | May 10, 2026, 10:28 a.m. |
Created at: April 27, 2026, 8:51 p.m.