Triple
T2561508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OLE DB |
E57250
|
entity |
| Predicate | supportsAccessTo |
P28414
|
FINISHED |
| Object | relational data sources |
—
|
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: relational data sources | Statement: [OLE DB, supportsAccessTo, relational data sources]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsAccessTo Context triple: [OLE DB, supportsAccessTo, relational data sources]
-
A.
controlsAccessTo
Indicates that one entity regulates, manages, or determines the ability of another entity to reach, use, or interact with a resource, location, or service.
-
B.
hasAccessTo
Indicates that one entity is permitted to enter, use, or interact with another entity, resource, or location.
-
C.
accessStatus
Indicates the current level or state of permission or availability for accessing a resource or entity.
-
D.
supportsACLs
Indicates that one entity provides or is compatible with access control lists (ACLs) for managing permissions on another entity.
-
E.
accessibleOn
chosen
Indicates that one entity can be reached, used, or obtained through another entity (such as a platform, device, or medium).
- 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_69ab4a4ef9008190a0e6d4422b9418b7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd35c6ee88190b6eaa1841d3e99a4 |
completed | March 7, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69abd0caeb488190b0dd8e48d0f2777d |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:48 p.m.