Triple
T32414619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MongoDB API |
E828306
|
entity |
| Predicate | supportsQuerySyntax |
P206269
|
FINISHED |
| Object | MongoDB query syntax |
—
|
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: MongoDB query syntax | Statement: [MongoDB API, supportsQuerySyntax, MongoDB query syntax]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsQuerySyntax Context triple: [MongoDB API, supportsQuerySyntax, MongoDB query syntax]
-
A.
supportsBooleanOperators
Indicates that the subject allows the use of Boolean operators (such as AND, OR, NOT) within its operations or expressions.
-
B.
supportsFieldQualifiers
Indicates that an entity can accept and correctly interpret additional qualifying attributes or modifiers applied to its fields.
-
C.
supportsSpatialQueries
Indicates that the subject system or component is capable of performing spatial (location- or geometry-based) queries on data.
-
D.
supportsExpressionType
Indicates that one entity is capable of handling, processing, or being compatible with a specified type of expression.
-
E.
supportsPlaceholderSyntax
Indicates that one entity provides or is compatible with a placeholder-based syntax used for parameterization or substitution in another entity.
- 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_69f34919f300819092b541c6277cd68a |
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:53 a.m.