Triple
T32481508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microsoft Cardfile for Windows 3.x versions |
E830119
|
entity |
| Predicate | supportsRelationalQueries |
P206290
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Microsoft Cardfile for Windows 3.x versions, supportsRelationalQueries, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsRelationalQueries Context triple: [Microsoft Cardfile for Windows 3.x versions, supportsRelationalQueries, no]
-
A.
supportsDatabaseConnectivity
Indicates that an entity provides the capability to establish and maintain connections to a database system.
-
B.
supportsSpatialQueries
Indicates that the subject system or component is capable of performing spatial (location- or geometry-based) queries on data.
-
C.
supportsRelation
Indicates that one entity provides assistance, endorsement, or structural backing to another entity or its activity.
-
D.
supportsAggregation
Indicates that one entity enables or allows another entity to be combined, grouped, or summarized with others through an aggregation operation.
-
E.
supportsPredicateFiltering
Indicates that the subject allows or enables filtering operations to be performed based on specific predicates or conditions.
- 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_69f3491ff3b48190b50a7fa00bb05b1f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 12:58 a.m.