Triple
T33748555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Husbands of Edith |
E864768
|
entity |
| Predicate | hasProtagonistGivenName |
P186374
|
FINISHED |
| Object | Edith |
E149275
|
NE 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: Edith | Statement: [The Husbands of Edith, hasProtagonistGivenName, Edith]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProtagonistGivenName Context triple: [The Husbands of Edith, hasProtagonistGivenName, Edith]
-
A.
hasProtagonist
Indicates that a work of narrative has a main character who serves as its central focus or driving agent.
-
B.
hasProtagonistNameInFilmAdaptation
Indicates that a specific name is used for the story’s main character in a particular film adaptation.
-
C.
hasLeadCharacterName
chosen
Indicates that an entity (such as a work or production) has a specified name for its primary or main character.
-
D.
protagonistAlsoKnownAs
Indicates that an entity serving as a protagonist is alternatively referred to by another name or alias.
-
E.
protagonistFullName
Indicates that the subject entity is the full, proper name (including given and family names) of the story’s main protagonist.
- F. None of above.
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_69f3498c35f881909df279ae4270f831 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a01c51e2d088190b9dcce5b6de1cb9b |
completed | May 11, 2026, 12:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36657758808190b438ed151246be63 |
completed | June 20, 2026, 10:03 a.m. |
| PD | Predicate disambiguation | batch_6a01c4c715a48190b7435de8a9d86fd4 |
completed | May 11, 2026, noon |
Created at: May 1, 2026, 1:45 a.m.