Triple
T37158325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mimsie |
E920571
|
entity |
| Predicate | associatedWithCompanyFounder |
P143912
|
FINISHED |
| Object | Mary Tyler Moore |
E70646
|
NE 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: Mary Tyler Moore | Statement: [Mimsie, associatedWithCompanyFounder, Mary Tyler Moore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithCompanyFounder Context triple: [Mimsie, associatedWithCompanyFounder, Mary Tyler Moore]
-
A.
companyFounderAssociated
chosen
Indicates that there is a notable connection or involvement between a company and an individual recognized as its founder.
-
B.
associatedWorkOfFounder
Indicates a relationship where a work (such as a publication, project, or creation) is linked to the person who founded or established it.
-
C.
hasParentCompanyFounder
Indicates that an entity is the founder of the parent company of another entity.
-
D.
coFounderCompany
Indicates that a person is one of the founding members who jointly established a particular company.
-
E.
hasCoFounderRoleOf
Indicates that one entity holds the role or position of co-founder in relation to another entity, such as an organization or venture.
- F. None of above.
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_69f76ea0429081908c711b55599eac3c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40360b7c388190885e2db6a514d1b2 |
completed | June 27, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:15 p.m.