Triple
T15108363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MongoDB Inc. |
E360845
|
entity |
| Predicate | Dwight MerrimanRole |
P117352
|
FINISHED |
| Object | Co-founder |
—
|
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: Co-founder | Statement: [MongoDB Inc., Dwight MerrimanRole, Co-founder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Dwight MerrimanRole Context triple: [MongoDB Inc., Dwight MerrimanRole, Co-founder]
-
A.
Jack Hively
Indicates a relationship or action involving the person named Jack Hively, such as authorship, direction, or participation in a work or event.
-
B.
Dan HartRole
Indicates that Dan Hart holds or performs a specific role, position, or function in relation to another entity or context.
-
C.
Lincoln Lewis
Indicates a relationship or association involving the entity or name "Lincoln Lewis," such as authorship, participation, or attribution in a given context.
-
D.
Ron Harper
Indicates a relationship or action involving Ron Harper, such as participation, association, or attribution connected to this individual.
-
E.
RobMorrowRole
Indicates that a person has played a specific role in a work featuring Rob Morrow.
- 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_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. |
| PDg | Predicate description generation | batch_69dec71e8dcc81908badc834b6ccf273 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:05 a.m.