Triple
T29791707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Jehnna |
E756424
|
entity |
| Predicate | franchiseCharacterType |
P132983
|
FINISHED |
| Object | supporting protagonist |
—
|
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 protagonist | Statement: [Princess Jehnna, franchiseCharacterType, supporting protagonist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: franchiseCharacterType Context triple: [Princess Jehnna, franchiseCharacterType, supporting protagonist]
-
A.
franchiseCharacter
Indicates a relationship where a character belongs to, appears in, or is part of a particular media franchise.
-
B.
franchiseOriginCharacter
Indicates that a character is the original or primary character from which a franchise or its derivative works originate.
-
C.
typeOfCharacter
Indicates that one entity is a specific kind or category of character in relation to another entity.
-
D.
franchiseElementType
chosen
Indicates the specific role or category that an element occupies within a franchise structure or system.
-
E.
franchiseCharacterCreator
Indicates that an entity is the creator or originator of a character that belongs to a particular franchise.
- 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_69f22454583081908927516cb9938d1d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67d3624248190a36a9b2d2e9778d4 |
completed | May 2, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 5:12 p.m.