Triple
T29739184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MQPUT |
E752547
|
entity |
| Predicate | supportsTransactionControl |
P207175
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [MQPUT, supportsTransactionControl, yes]
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 (4 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_69f0d62b064081908c1ae61cd68fb139 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 28, 2026, 7:47 p.m.