Triple
T15108455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MongoDB |
E360848
|
entity |
| Predicate | supportsIndexing |
P109813
|
FINISHED |
| Object | single-field indexes |
—
|
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: single-field indexes | Statement: [MongoDB, supportsIndexing, single-field indexes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsIndexing Context triple: [MongoDB, supportsIndexing, single-field indexes]
-
A.
usesIndexation
chosen
Indicates that one entity applies or relies on an indexing scheme or index-based method provided by or associated with another entity.
-
B.
hasIndexing
Indicates that one entity organizes, catalogs, or references another entity using an index or indexing system.
-
C.
indexingService
Indicates a service that organizes, catalogs, and maintains an index of items or data so they can be efficiently searched and retrieved.
-
D.
isSearchable
Indicates that the referenced entity can be discovered or retrieved through a search operation or query.
-
E.
supportsDocument
Indicates that one entity provides compatibility or functionality for handling, processing, or using a particular document or document type.
- 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_69d85a0491ec8190830960be8fafb994 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0058af8988190977d998f85893836 |
completed | April 15, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69deb96c1d9c81909351558ed97bc5b7 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:05 a.m.