Triple
T25886823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baylie Cregut |
E652210
|
entity |
| Predicate | castMemberOfSitcom |
P107267
|
FINISHED |
| Object | Raising Hope |
—
|
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: Raising Hope | Statement: [Baylie Cregut, castMemberOfSitcom, Raising Hope]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: castMemberOfSitcom Context triple: [Baylie Cregut, castMemberOfSitcom, Raising Hope]
-
A.
memberOfTelevisionShowCast
chosen
Indicates that a person is a member of the cast of a particular television show.
-
B.
relatedCastMember
Indicates that two cast members are connected through a relevant relationship, such as working together on the same production or being otherwise professionally associated.
-
C.
alsoPortrayedBy
Indicates that the same role or character is portrayed by an additional, different performer or actor.
-
D.
portrayedByAlsoPlays
Indicates that the actor who portrays a given character also plays another specified role or character.
-
E.
castMemberWith
Indicates that one entity is a cast member appearing together with another specified entity in the same production or work.
- 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_69e7ab3b92cc81908febd90317862647 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6034386208190a54585ce1e3ef5d1 |
completed | May 2, 2026, 1:59 p.m. |
| PD | Predicate disambiguation | batch_69f4a0fed15881909b789251fe5d8d45 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 22, 2026, 8:18 a.m.