Triple
T28523512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Home |
E721848
|
entity |
| Predicate | primaryNarrativeFocalCharacter |
P9202
|
FINISHED |
| Object | Glory Boughton |
—
|
NE NERFINISHED |
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: Glory Boughton | Statement: [Home, primaryNarrativeFocalCharacter, Glory Boughton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryNarrativeFocalCharacter Context triple: [Home, primaryNarrativeFocalCharacter, Glory Boughton]
-
A.
narrativeCharacter
Indicates that one entity functions as a character within the narrative or story associated with another entity.
-
B.
mainProtagonist
chosen
Indicates that the subject is the central character or primary focus in the narrative of the related work.
-
C.
protagonistIs
Indicates that one entity serves as the main character or central figure in relation to another entity or narrative context.
-
D.
primaryActor
Indicates that the referenced entity is the main participant or most central party responsible for the action or event in the relationship.
-
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_69f01a5cbcc4819083fb4e723378713e |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_6a004b6ad4248190b402a0d01b0ebf83 |
completed | May 10, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_6a004ae736b881908a0efed8f63f982e |
completed | May 10, 2026, 9:07 a.m. |
Created at: April 28, 2026, 3:22 a.m.