Triple
T4029884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Blue-Eyed Manchu |
E83681
|
entity |
| Predicate | hasProtagonistDescriptor |
P21183
|
FINISHED |
| Object | blue-eyed Manchu 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: blue-eyed Manchu character | Statement: [The Blue-Eyed Manchu, hasProtagonistDescriptor, blue-eyed Manchu character]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProtagonistDescriptor Context triple: [The Blue-Eyed Manchu, hasProtagonistDescriptor, blue-eyed Manchu character]
-
A.
hasProtagonist
Indicates that a work of narrative has a main character who serves as its central focus or driving agent.
-
B.
protagonistDescription
chosen
Indicates that a text provides a descriptive summary or characterization of the story’s main protagonist.
-
C.
protagonistIs
Indicates that one entity serves as the main character or central figure in relation to another entity or narrative context.
-
D.
mainProtagonist
Indicates that the subject is the central character or primary focus in the narrative of the related work.
-
E.
protagonistField
Indicates that the subject is the main or central character (protagonist) within the specified narrative or context.
- 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_69aed92e29ac819080f7a98b594fec05 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaf1d8208190951a20ad7e5ab7bc |
completed | March 9, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69aef8fe440c819093a7fa22c4ff3f1a |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:36 p.m.