Triple
T34569312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Postmaster’s Daughter |
E887578
|
entity |
| Predicate | writtenByPseudonym |
P72674
|
FINISHED |
| Object | Gordon Holmes |
—
|
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: Gordon Holmes | Statement: [The Postmaster’s Daughter, writtenByPseudonym, Gordon Holmes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writtenByPseudonym Context triple: [The Postmaster’s Daughter, writtenByPseudonym, Gordon Holmes]
-
A.
firstPublishedUnderPseudonym
Indicates that a work’s initial publication occurred under a pseudonym rather than the creator’s real name.
-
B.
revealedAsPseudonymIn
Indicates that one identity or name is disclosed or recognized as a pseudonym within a particular context, work, or source.
-
C.
pseudonymOfWriter
chosen
Indicates that one entity is a pseudonym used by a writer who is represented by the other entity.
-
D.
pseudonymCoinedBy
Indicates that a particular pseudonym was created or invented by a specific agent or source.
-
E.
pseudonymInspiredBy
Indicates that a pseudonym was chosen or created based on, or in homage to, another name, person, work, or concept.
- 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_69f349d1a5fc81908557a46875b2f157 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f728a345488190bd7e6751b09ac591 |
completed | May 3, 2026, 10:51 a.m. |
| PD | Predicate disambiguation | batch_69f7283ef2608190a7a85d7e7f5332c0 |
completed | May 3, 2026, 10:49 a.m. |
Created at: May 1, 2026, 2:02 a.m.