Triple
T27850932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jet Database Engine |
E703949
|
entity |
| Predicate | supportsAccessVersion |
P55140
|
FINISHED |
| Object | Microsoft Access 1.0 |
—
|
NE NERFINISHED |
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: Microsoft Access 1.0 | Statement: [Jet Database Engine, supportsAccessVersion, Microsoft Access 1.0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsAccessVersion Context triple: [Jet Database Engine, supportsAccessVersion, Microsoft Access 1.0]
-
A.
supportsVersioning
Indicates that the subject provides or is compatible with functionality for managing and maintaining multiple versions of an item or resource.
-
B.
supportsSinceVersion
Indicates that a given entity has provided support or compatibility for another entity starting from a specified version onward.
-
C.
supportsSpecificationVersion
chosen
Indicates that one entity is compatible with and able to operate according to a particular version of a specification.
-
D.
supportsSince
Indicates that one entity has been providing support to another entity starting from a specific point in time and continuing thereafter.
-
E.
supportsAccessModel
Indicates that one entity enables, permits, or is compatible with a particular access model used by another 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_69ef840e614c8190a88cf9638c14a265 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_6a0019b0e9fc81909494320f05e81742 |
completed | May 10, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_6a00193379e0819096d1985686ce10e3 |
completed | May 10, 2026, 5:35 a.m. |
Created at: April 27, 2026, 6:10 p.m.