Triple
T15108359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MongoDB Inc. |
E360845
|
entity |
| Predicate | Dev IttycheriaRole |
P2568
|
FINISHED |
| Object | Chief Executive Officer |
—
|
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: Chief Executive Officer | Statement: [MongoDB Inc., Dev IttycheriaRole, Chief Executive Officer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Dev IttycheriaRole Context triple: [MongoDB Inc., Dev IttycheriaRole, Chief Executive Officer]
-
A.
hasChiefExecutiveRole
chosen
Indicates that an entity holds the highest executive leadership position and overall managerial authority within an organization.
-
B.
ethnicRole
Indicates a role, function, or social position that is specifically associated with or defined by an entity’s ethnicity.
-
C.
CorwinRole
Indicates that an entity holds or is assigned a specific role or function in relation to Corwin.
-
D.
deFactoRole
Indicates that an entity effectively functions in a role or capacity in practice, even if that role is not formally or officially assigned.
-
E.
roleAtD.C.United
Indicates that an entity holds or held a specific role or position within the D.C. United soccer organization.
- 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.