Triple
T28079706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Presto |
E709642
|
entity |
| Predicate | supportsTransfers |
P89762
|
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, supportsTransfers, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsTransfers Context triple: [Presto, supportsTransfers, true]
-
A.
hasTransferOption
chosen
Indicates that there exists a way or method for something (e.g., funds, data, ownership, or passengers) to be transferred from one entity or location to another.
-
B.
supportsExchangeBetween
Indicates that one entity enables or facilitates the exchange or transfer of something (e.g., data, value, or resources) between two or more other entities.
-
C.
hasTransfer
Indicates a relationship where something is moved or conveyed from one entity or location to another.
-
D.
supportsTransactions
Indicates that one entity provides the capability for another entity to perform or manage transactions reliably.
-
E.
allowsTransferTo
Indicates that one entity permits or enables the transfer of something (such as rights, funds, or data) to another specified entity.
- 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_6a005d878aec81908e1177914a8fb610 |
completed | May 10, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_6a005c382f8881908ff33ebb7f88c430 |
completed | May 10, 2026, 10:21 a.m. |
Created at: April 27, 2026, 8:51 p.m.