Triple
T3645684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bianca |
E77294
|
entity |
| Predicate | playsRoleInStory |
P42552
|
FINISHED |
| Object | supporting character |
—
|
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 character | Statement: [Bianca, playsRoleInStory, supporting character]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsRoleInStory Context triple: [Bianca, playsRoleInStory, supporting character]
-
A.
roleInStories
chosen
Indicates the specific function, position, or character part an entity plays within one or more stories.
-
B.
playsInRole
Indicates that an entity performs or appears in a specific role within a production, event, or context.
-
C.
playedRoleIn
Indicates that an entity performed or assumed a specific role or character within a particular event, production, or context.
-
D.
roleInScene
Indicates that an entity participates in a particular scene with a specific role or function within that scene.
-
E.
narrativeCharacter
Indicates that one entity functions as a character within the narrative or story associated with another entity.
- 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_69ad85de1b988190a45f8dbfebc806fc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc35da84c81908950de92ba171fa3 |
completed | March 8, 2026, 6:43 p.m. |
| PD | Predicate disambiguation | batch_69adb8445b2c8190ab07f6ad4e010d0e |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:24 p.m.