Triple
T28302001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cravings by Chrissy Teigen |
E713733
|
entity |
| Predicate | hasBrandFounderRole |
P173243
|
FINISHED |
| Object | Chrissy Teigen |
—
|
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: Chrissy Teigen | Statement: [Cravings by Chrissy Teigen, hasBrandFounderRole, Chrissy Teigen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBrandFounderRole Context triple: [Cravings by Chrissy Teigen, hasBrandFounderRole, Chrissy Teigen]
-
A.
founderAlsoKnownAs
Indicates that an individual who is a founder of something is also known by an alternative name or alias.
-
B.
founderKnownFor
Indicates that a founder is particularly recognized or notable for a specific work, achievement, product, or contribution.
-
C.
hasFounderName
Indicates that an entity has a founder whose personal name is given by the associated value.
-
D.
hasFounderRelationship
Indicates a relationship where one entity serves as the founder or co-founder of another entity.
-
E.
labelFounder
Indicates that one entity is the founder or creator of another entity, such as an organization, project, or initiative.
- 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_69efb524ab688190a1ce7ee7c9520932 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6b342499c8190b85009a3f0f179e4 |
completed | May 3, 2026, 2:30 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b2a31e008190aacef03c2ebe5787 |
completed | May 3, 2026, 2:27 a.m. |
Created at: April 27, 2026, 11:35 p.m.