Triple
T30032505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catch Me If You Can (stage musical) |
E763058
|
entity |
| Predicate | roleDepicted |
P54972
|
FINISHED |
| Object | Frank Abagnale Jr. |
—
|
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: Frank Abagnale Jr. | Statement: [Catch Me If You Can (stage musical), roleDepicted, Frank Abagnale Jr.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleDepicted Context triple: [Catch Me If You Can (stage musical), roleDepicted, Frank Abagnale Jr.]
-
A.
depictsPersonRole
Indicates that an image or representation shows a person in a specific role, function, or capacity.
-
B.
representedRole
Indicates that one entity serves as a stand-in, proxy, or representative performing a role on behalf of another entity.
-
C.
roleOfCharacter
Indicates that one entity serves as the narrative or functional role played by a character within a story, scenario, or context.
-
D.
roleCharacteristic
Indicates that a particular characteristic, quality, or attribute is associated with and helps define a given role or function.
-
E.
characterPortrayedIs
chosen
Indicates that one entity serves as the fictional or dramatic role that is depicted or played by another entity.
- 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_69f2246fb2b88190acff36bf7975c8f0 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f679b10fd881909bd58f996462c258 |
completed | May 2, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:50 p.m.