Triple
T37367922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legend (2015 film) |
E927760
|
entity |
| Predicate | hasColinMorganRole |
P142919
|
FINISHED |
| Object | Frank Shea |
E1013314
|
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: Frank Shea | Statement: [Legend (2015 film), hasColinMorganRole, Frank Shea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasColinMorganRole Context triple: [Legend (2015 film), hasColinMorganRole, Frank Shea]
-
A.
roleColinMorgan
chosen
Indicates that an entity has the role or character portrayed by Colin Morgan in a given context or work.
-
B.
hasDennisMorganRole
Indicates that an entity holds or is assigned the specific role associated with Dennis Morgan.
-
C.
hasCrewRole
Indicates that an entity serves in a specific role or position within a crew associated with another entity.
-
D.
hasPortrayedPersonRole
Indicates that an entity has performed or held a specific role in portraying a particular person (e.g., in a film, play, or other representation).
-
E.
hasHumanCast
Indicates that a work or production features human performers as part of its cast.
- 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_69f76eb820248190a5c395ca50ad002a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a5a0402bdc881908e93e05bebdc9196 |
completed | July 17, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:16 p.m.