Triple
T27420256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosalind Ivan |
E693020
|
entity |
| Predicate | hasTypeOfAppearance |
P93610
|
FINISHED |
| Object | supporting roles |
—
|
LITERAL 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: supporting roles | Statement: [Rosalind Ivan, hasTypeOfAppearance, supporting roles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfAppearance Context triple: [Rosalind Ivan, hasTypeOfAppearance, supporting roles]
-
A.
hasCharacterAppearance
Indicates that a character appears or is visually represented within a given work, scene, or context.
-
B.
hasMediaAppearanceIn
Indicates that an entity appears or is featured as media content within a specified media work, program, or publication.
-
C.
allegedAppearanceType
Indicates the type or nature of an appearance that is claimed or reported to have occurred, without confirming that the appearance actually took place.
-
D.
hasTypicalAppearance
Indicates that an entity exhibits the standard or commonly expected visual form or look associated with its kind.
-
E.
hasScreenAppearanceType
chosen
Indicates the type or manner in which an entity appears or is presented on a screen.
- 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_69ef5208617081908f731d312e0fd1bc |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: April 27, 2026, 12:35 p.m.