Triple
T33872640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jason Segel as Nick Andopolis |
E868258
|
entity |
| Predicate | breakoutRoleFor |
P134231
|
FINISHED |
| Object | Jason Segel |
—
|
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: Jason Segel | Statement: [Jason Segel as Nick Andopolis, breakoutRoleFor, Jason Segel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: breakoutRoleFor Context triple: [Jason Segel as Nick Andopolis, breakoutRoleFor, Jason Segel]
-
A.
hasBreakthroughRoleFor
chosen
Indicates that an entity serves as a major, career-defining or pivotal role for another entity, marking a significant breakthrough or turning point.
-
B.
creditedRoleOf
Indicates that a particular role or position is formally acknowledged as being held or performed by a specific entity in a credit or attribution context.
-
C.
knownForRoleIn
Indicates that an entity is recognized or notable for performing a particular role in a specific work, project, or context.
-
D.
screenDebutInMajorRoleFor
Indicates that one entity made their first significant on-screen appearance (major role) in a particular production or work.
-
E.
leadRoleActor
Indicates that an actor performs a leading or principal role in a work or production.
- 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_69f34995029081909ede0f7df73d1a5e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70102f44481909880ca55459e2336 |
completed | May 3, 2026, 8:02 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5a4f7881909324eb3c20ca96f1 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:47 a.m.