Triple
T38473027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The New Perry Mason |
E915470
|
entity |
| Predicate | roleOfHamiltonBurgerPlayedBy |
P9616
|
FINISHED |
| Object | Harry Guardino |
E360259
|
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: Harry Guardino | Statement: [The New Perry Mason, roleOfHamiltonBurgerPlayedBy, Harry Guardino]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleOfHamiltonBurgerPlayedBy Context triple: [The New Perry Mason, roleOfHamiltonBurgerPlayedBy, Harry Guardino]
-
A.
playedBy
chosen
Indicates that a role, character, or performance is portrayed or executed by a specific person or agent.
-
B.
portrayedInBroadwayProductionBy
Indicates that an entity was depicted or performed in a Broadway stage production by a specified person or group.
-
C.
roleInTheMarvelousMrsMaisel
Indicates that an entity has a role or appearance in the television series "The Marvelous Mrs. Maisel."
-
D.
roleInHaroldAndKumarSeries
Indicates that an entity portrays a character in the Harold and Kumar film series.
-
E.
broadwayLeadActor
Indicates that the subject is the principal or starring actor in a Broadway production associated with the object.
- 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_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41d64b50f481908ba2524db62d726b |
completed | June 29, 2026, 2:19 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
Created at: May 3, 2026, 4:31 p.m.