Triple
T32414644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MongoDB API |
E828306
|
entity |
| Predicate | mayDifferFromMongoDB |
P53790
|
FINISHED |
| Object | feature coverage |
—
|
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: feature coverage | Statement: [MongoDB API, mayDifferFromMongoDB, feature coverage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayDifferFromMongoDB Context triple: [MongoDB API, mayDifferFromMongoDB, feature coverage]
-
A.
mayDifferFrom
chosen
Indicates that one entity is allowed or expected to be different from another entity, without requiring them to be identical.
-
B.
migrationCompatibilityWith
Indicates that one entity can be transitioned, upgraded, or moved to another entity or environment without incompatibilities or conflicts.
-
C.
differIn
Indicates that two entities are not the same in at least one specified aspect, attribute, or value.
-
D.
mayBeEqualTo
Indicates that two entities are possibly equal, but their equality is uncertain or not definitively established.
-
E.
migrationPolicy
Indicates the rules or strategies governing how entities move, transfer, or transition from one context, location, or state to another.
- 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_69f34919f300819092b541c6277cd68a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c25bb38881909a5a0552b316e970 |
completed | May 3, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:53 a.m.