Triple
T33506258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agent Hamilton films |
E858118
|
entity |
| Predicate | hasLeadRolePlayedBy |
P166850
|
FINISHED |
| Object | Mikael Persbrandt |
—
|
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: Mikael Persbrandt | Statement: [Agent Hamilton films, hasLeadRolePlayedBy, Mikael Persbrandt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLeadRolePlayedBy Context triple: [Agent Hamilton films, hasLeadRolePlayedBy, Mikael Persbrandt]
-
A.
replacesInLeadRole
Indicates that one entity takes over or substitutes for another entity in the primary or leading role within a given context or production.
-
B.
leadRoleActor
chosen
Indicates that an actor performs a leading or principal role in a work or production.
-
C.
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).
-
D.
playedBy
Indicates that a role, character, or performance is portrayed or executed by a specific person or agent.
-
E.
hasPortrayedRole
Indicates that an entity has performed or depicted a specific role or character, typically in a work such as a film, play, or television show.
- 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_69f3497721848190978fbee5e0a526f8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
Created at: May 1, 2026, 1:38 a.m.