Triple
T8493667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norby, the Mixed-Up Robot |
E201038
|
entity |
| Predicate | coProtagonistDescription |
P32032
|
FINISHED |
| Object | young human companion |
—
|
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 companion | Statement: [Norby, the Mixed-Up Robot, coProtagonistDescription, young human companion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coProtagonistDescription Context triple: [Norby, the Mixed-Up Robot, coProtagonistDescription, young human companion]
-
A.
coProtagonist
chosen
Indicates that two or more entities share the primary leading role together in the same narrative work.
-
B.
protagonistDescription
Indicates that a text provides a descriptive summary or characterization of the story’s main protagonist.
-
C.
mainProtagonist
Indicates that the subject is the central character or primary focus in the narrative of the related work.
-
D.
protagonistType
Indicates the role or category that the main character (protagonist) of a story or scenario belongs to.
-
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.
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_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. |
Created at: March 30, 2026, 6:13 p.m.