Triple
T29739184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MQPUT |
E752547
|
entity |
| Predicate | supportsTransactionControl |
—
|
GENERATED |
| Object | yes |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsTransactionControl Context triple: [MQPUT, supportsTransactionControl, yes]
-
A.
supportsTransactions
Indicates that one entity provides the capability for another entity to perform or manage transactions reliably.
-
B.
supportsTransactionIsolationLevel
Indicates that an entity (such as a system, component, or resource) is capable of operating with or honoring a specified transaction isolation level.
-
C.
usesTransaction
Indicates that one entity conducts or performs an action by means of a specific transaction or transactional process.
-
D.
supportsTransactionalWFS
Indicates that the subject provides or is compatible with a transactional Web Feature Service (WFS-T), allowing create, update, and delete operations on geospatial features.
-
E.
supportsDatabaseConnectivity
Indicates that an entity provides the capability to establish and maintain connections to a database system.
- F. None of above. chosen
Provenance (1 batch)
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_69f0d62b064081908c1ae61cd68fb139 |
completed | April 28, 2026, 3:45 p.m. |
Created at: April 28, 2026, 7:47 p.m.