Triple
T25504423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Bride / Mary Shelley in "Bride of Frankenstein" |
E639209
|
entity |
| Predicate | roleComponent |
P158605
|
FINISHED |
| Object | The Bride |
—
|
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: The Bride | Statement: [The Bride / Mary Shelley in "Bride of Frankenstein", roleComponent, The Bride]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleComponent Context triple: [The Bride / Mary Shelley in "Bride of Frankenstein", roleComponent, The Bride]
-
A.
roleWith
Indicates that one entity holds or performs a particular role in relation to another entity.
-
B.
roleAccordingTo
Indicates that an entity holds a particular role or function as defined or interpreted by a specified source or perspective.
-
C.
roleInOperation
Indicates that an entity holds a specific function, duty, or position within a particular operation or activity.
-
D.
unitRole
Indicates the functional role or purpose that a unit serves within a larger system or context.
-
E.
authorityRole
Indicates that one entity holds an official position or role that grants it authority or control over another entity or within a specific context.
- 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_69e75dbd09308190b6b5f0afdc12ec6d |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f804c9f48190be4e560a60ee6242 |
completed | May 2, 2026, 1:11 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 21, 2026, 2:46 p.m.