Triple
T33476623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robertson family |
E857339
|
entity |
| Predicate | businessFoundedBy |
P46924
|
FINISHED |
| Object | Phil Robertson |
—
|
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: Phil Robertson | Statement: [Robertson family, businessFoundedBy, Phil Robertson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: businessFoundedBy Context triple: [Robertson family, businessFoundedBy, Phil Robertson]
-
A.
founderKnownFor
Indicates that a founder is particularly recognized or notable for a specific work, achievement, product, or contribution.
-
B.
businessFoundedIn
Indicates that a business entity was established or came into existence in a specific location or time.
-
C.
foundedCompany
chosen
Indicates that an entity established or created a company, typically as its founder or co-founder.
-
D.
companyFounderAssociated
Indicates that there is a notable connection or involvement between a company and an individual recognized as its founder.
-
E.
possiblyFoundedBy
Indicates that an entity may have been founded or established by another entity, but this founding relationship is uncertain or not definitively confirmed.
- 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_69f3497472508190b300ebd3fd402367 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e5029d88819082552ffa0b0e6313 |
completed | May 3, 2026, 6:02 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:38 a.m.