Triple
T24326600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Invisible Ghost |
E613116
|
entity |
| Predicate | hasNotableSupportingRole |
P90271
|
FINISHED |
| Object | Clarence Muse |
—
|
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: Clarence Muse | Statement: [The Invisible Ghost, hasNotableSupportingRole, Clarence Muse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableSupportingRole Context triple: [The Invisible Ghost, hasNotableSupportingRole, Clarence Muse]
-
A.
hasProminentSupportingActor
chosen
Indicates that an entity (such as a film or show) features a supporting actor whose role or recognition is notably significant within that work.
-
B.
has part in role
Indicates that an entity participates as a component or constituent specifically in a defined role within a larger whole or process.
-
C.
supportingActressRole
Indicates that an actress performs a supporting (non-leading) role in a particular production or work.
-
D.
hasMainRole
Indicates that an entity holds the primary or most significant role in relation to another entity or context.
-
E.
hasNotableRoleIn
Indicates that an entity holds a significant or noteworthy role or function within another entity, event, work, or context.
- 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_69e2d7db6d5c819091194918157a7c1f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292edb6f481909f0a6a7592fd7d6a |
completed | April 29, 2026, 11:23 p.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 1:54 a.m.