Triple
T15108508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MongoDB |
E360848
|
entity |
| Predicate | supportsShardingStrategy |
P82550
|
FINISHED |
| Object | range-based sharding |
—
|
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: range-based sharding | Statement: [MongoDB, supportsShardingStrategy, range-based sharding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsShardingStrategy Context triple: [MongoDB, supportsShardingStrategy, range-based sharding]
-
A.
supportsMultiTenancy
Indicates that the subject system or component is capable of serving and isolating multiple distinct tenants or customer environments within a single deployment.
-
B.
supportsPartitionStyle
chosen
Indicates that one entity is compatible with or able to work with a specified partition style used by another entity.
-
C.
supportsMultiblockAllocation
Indicates that an entity can handle allocating or managing multiple blocks of resources or memory in a single operation.
-
D.
supportsHierarchicalRouting
Indicates that one entity enables or is compatible with routing that uses a multi-level or hierarchical structure of routing domains or paths.
-
E.
isSupportedFor
Indicates that one entity provides compatibility, assistance, or backing necessary for another entity’s proper use or operation.
- 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.