Triple
T16563104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rocket Companies, Inc. |
E402388
|
entity |
| Predicate | roleOfVarunKrishna |
P124071
|
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: [Rocket Companies, Inc., roleOfVarunKrishna, Chief Executive Officer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleOfVarunKrishna Context triple: [Rocket Companies, Inc., roleOfVarunKrishna, Chief Executive Officer]
-
A.
roleInKrishnaLife
Indicates the specific role or function an entity plays in the life, activities, or narrative associated with Krishna.
-
B.
roleInRishiRichProject
Indicates that an entity holds or held a specific role or function within the Rishi Rich Project.
-
C.
typeOfWorkHeIsKnownFor
Indicates the category or kind of work for which a person is recognized or notable.
-
D.
roleInCarnaticWars
Indicates the role or involvement an entity had in the events of the Carnatic Wars.
-
E.
roleInVox
Indicates that an entity holds a specific role or function within a Vox-related context, such as a project, system, or organization named or described as "Vox."
- 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_69d8838648088190acf97ef11fc3f61b |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3576f757881909bfc6611361ed16d |
completed | April 18, 2026, 10:05 a.m. |
| PD | Predicate disambiguation | batch_69e296a47b7481909d9958158510c806 |
completed | April 17, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69e2d7f97e548190a474691a152bd8e8 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:15 a.m.