Triple
T8493721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norby and the Lost Princess |
E201040
|
entity |
| Predicate | secondaryProtagonistType |
P83031
|
FINISHED |
| Object | young human |
—
|
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: young human | Statement: [Norby and the Lost Princess, secondaryProtagonistType, young human]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryProtagonistType Context triple: [Norby and the Lost Princess, secondaryProtagonistType, young human]
-
A.
secondaryProtagonistCelebrated
Indicates that a secondary protagonist is being honored, praised, or widely recognized for their actions or role.
-
B.
protagonistType
Indicates the role or category that the main character (protagonist) of a story or scenario belongs to.
-
C.
coProtagonist
Indicates that two or more entities share the primary leading role together in the same narrative work.
-
D.
mainProtagonist
Indicates that the subject is the central character or primary focus in the narrative of the related work.
-
E.
protagonistAlterEgoOf
Indicates that one entity is the alternate identity or secret persona of the main character (protagonist) in a narrative.
- 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_69ca831ee390819095fae73400bbfafc |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe579b7088190b297b04527e36a2b |
completed | March 31, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cbd10a4b0881909e254117780dc823 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe30d453481908f897ed2b06e7534 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:13 p.m.