Triple
T32414620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MongoDB API |
E828306
|
entity |
| Predicate | supportsDriverCompatibility |
P86382
|
FINISHED |
| Object | MongoDB drivers |
E1138554
|
NE 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: MongoDB drivers | Statement: [MongoDB API, supportsDriverCompatibility, MongoDB drivers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDriverCompatibility Context triple: [MongoDB API, supportsDriverCompatibility, MongoDB drivers]
-
A.
supportsDriverType
chosen
Indicates that one entity is compatible with, or able to operate using, a specified type of driver.
-
B.
supportsDriverModel
Indicates that one entity provides compatibility with, or operational backing for, a specified driver model used to interface with hardware or software components.
-
C.
hasHardwareCompatibilityWith
Indicates that two hardware components or systems can operate together correctly and reliably without conflicts or incompatibilities.
-
D.
automationCompatibility
Indicates that one entity can be reliably and effectively operated, controlled, or integrated through automated systems or processes in relation to another entity.
-
E.
hasSoftwareCompatibilityWith
Indicates that one software system can operate correctly and effectively with another software system, without conflicts or required modifications.
- F. None of above.
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_69f34919f300819092b541c6277cd68a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a344f1fd52481908645912dec8d1953 |
completed | June 18, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:53 a.m.