Triple
T38473025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The New Perry Mason |
E915470
|
entity |
| Predicate | roleOfPaulDrakePlayedBy |
P9616
|
FINISHED |
| Object | Albert Stratton |
E2272048
|
NE 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: Albert Stratton | Statement: [The New Perry Mason, roleOfPaulDrakePlayedBy, Albert Stratton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleOfPaulDrakePlayedBy Context triple: [The New Perry Mason, roleOfPaulDrakePlayedBy, Albert Stratton]
-
A.
apprenticeRolePlayedBy
Indicates that an apprentice role is portrayed or performed by a specific person or actor.
-
B.
hasDrDreRole
Indicates that an entity holds or is assigned a specific role related to Dr. Dre (e.g., professional, creative, or collaborative capacity) in relation to another entity.
-
C.
playedBy
chosen
Indicates that a role, character, or performance is portrayed or executed by a specific person or agent.
-
D.
playsInRole
Indicates that an entity performs or appears in a specific role within a production, event, or context.
-
E.
roleInHaroldAndKumarSeries
Indicates that an entity portrays a character in the Harold and Kumar film series.
- F. None of above.
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_69f76e8ff5cc8190a88803369183845e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41d6498f9481909895f9639e32ea76 |
completed | June 29, 2026, 2:19 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
Created at: May 3, 2026, 4:31 p.m.