Triple
T26964609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Topaze (1933 film) |
E679137
|
entity |
| Predicate | featuresEarlyProminentRoleFor |
P192274
|
FINISHED |
| Object | Myrna Loy |
—
|
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: Myrna Loy | Statement: [Topaze (1933 film), featuresEarlyProminentRoleFor, Myrna Loy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresEarlyProminentRoleFor Context triple: [Topaze (1933 film), featuresEarlyProminentRoleFor, Myrna Loy]
-
A.
promotionalRole
Indicates that an entity serves in a capacity focused on promoting, advertising, or publicizing another entity, product, or activity.
-
B.
featuresCharacterRole
Indicates that a work includes a character appearing in a specific narrative or functional role.
-
C.
possibleRole
Indicates that an entity is capable of or eligible to serve in a particular role or function in a given context.
-
D.
profileRole
Indicates the specific role or function an entity holds within a given profile or contextual configuration.
-
E.
loreRole
Indicates the specific narrative or canonical function an entity fulfills within a fictional or mythological lore.
- F. None of above. chosen
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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
| PDg | Predicate description generation | batch_69fd05b965608190a3666410b9f8e125 |
completed | May 7, 2026, 9:35 p.m. |
Created at: April 27, 2026, 6:34 a.m.