Triple
T33878745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wide Sargasso Sea |
E868426
|
entity |
| Predicate | alternativeNameForCharacter |
P41555
|
FINISHED |
| Object | Antoinette Cosway is Bertha Mason |
—
|
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: Antoinette Cosway is Bertha Mason | Statement: [Wide Sargasso Sea, alternativeNameForCharacter, Antoinette Cosway is Bertha Mason]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alternativeNameForCharacter Context triple: [Wide Sargasso Sea, alternativeNameForCharacter, Antoinette Cosway is Bertha Mason]
-
A.
characterAlias
chosen
Indicates that one character is known or referred to by an alternative name or alias.
-
B.
protagonistAlsoKnownAs
Indicates that an entity serving as a protagonist is alternatively referred to by another name or alias.
-
C.
associatedWithCharacterAlias
Indicates that one entity is linked to or connected with an alternative name or alias used for a particular character.
-
D.
characterName
Indicates that an entity has a specific name used to identify its character.
-
E.
characterFullName
Indicates that the predicate specifies the complete, formal name of a character.
- 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_69f34995b81c8190acdb45cea5a10eff |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: May 1, 2026, 1:48 a.m.