Triple
T32481506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microsoft Cardfile for Windows 3.x versions |
E830119
|
entity |
| Predicate | supportsRichText |
—
|
GENERATED |
| Object | no |
—
|
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: supportsRichText Context triple: [Microsoft Cardfile for Windows 3.x versions, supportsRichText, no]
-
A.
supportsTextFormat
chosen
Indicates that one entity is capable of handling, rendering, or otherwise working with a specified text format.
-
B.
supportsMarkdown
Indicates that one entity provides the ability for another entity to use or display content formatted in Markdown.
-
C.
supportsNarrativeText
Indicates that one entity provides justification, evidence, or contextual backing that helps explain or validate the narrative content expressed by another entity.
-
D.
isFeatureRich
Indicates that an entity possesses a large number and wide variety of capabilities or functionalities.
-
E.
supportsFeature
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
- F. None of above.
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_69f3491ff3b48190b50a7fa00bb05b1f |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:58 a.m.