Triple
T25475452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red McCombs |
E638418
|
entity |
| Predicate | employerOrFounderOf |
P143912
|
FINISHED |
| Object | Red McCombs Automotive Group |
—
|
NE NERFINISHED |
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: Red McCombs Automotive Group | Statement: [Red McCombs, employerOrFounderOf, Red McCombs Automotive Group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: employerOrFounderOf Context triple: [Red McCombs, employerOrFounderOf, Red McCombs Automotive Group]
-
A.
workIncludesRoleOfFounder
Indicates that a work involves or credits an entity in the specific role of founder.
-
B.
associatedProfessionOfFounder
Indicates the professional field or occupation linked to the founder of an entity.
-
C.
coFounderCompany
Indicates that a person is one of the founding members who jointly established a particular company.
-
D.
associatedWorkOfFounder
Indicates a relationship where a work (such as a publication, project, or creation) is linked to the person who founded or established it.
-
E.
companyFounderAssociated
chosen
Indicates that there is a notable connection or involvement between a company and an individual recognized as its founder.
- 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_69e75db9b964819096802dcf502e577e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 21, 2026, 2:25 p.m.