Triple
T15709564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richard Dreyfuss as Dr. Leo Marvin |
E380802
|
entity |
| Predicate | creditedCastStatus |
P5563
|
FINISHED |
| Object | leading role |
—
|
LITERAL FINISHED |
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: leading role | Statement: [Richard Dreyfuss as Dr. Leo Marvin, creditedCastStatus, leading role]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creditedCastStatus Context triple: [Richard Dreyfuss as Dr. Leo Marvin, creditedCastStatus, leading role]
-
A.
creditedIn
Indicates that an entity is acknowledged or listed as a contributor or source within a particular work, record, or context.
-
B.
includesCastMembersFrom
Indicates that one entity’s cast list contains one or more cast members who also appear in the cast list of another entity.
-
C.
cast
Indicates that an agent selects and assigns a person or thing to play a specific role or function in a production or context.
-
D.
starredActor
chosen
Indicates that an actor performed a leading or significant role in a particular production or work.
-
E.
originalCast
Indicates that the subject is a member of the initial group of performers or participants who first originated a role 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_69d86d9bf930819082b30cf6d169297c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04f8d8b648190842c635f2ae7bfa4 |
completed | April 16, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69e00526759c819088b80d85138b8974 |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:45 a.m.