Triple
T25703210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Female Spectator |
E644518
|
entity |
| Predicate | pseudonymousEditor |
P56608
|
FINISHED |
| Object | The Female Spectator |
—
|
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: The Female Spectator | Statement: [The Female Spectator, pseudonymousEditor, The Female Spectator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pseudonymousEditor Context triple: [The Female Spectator, pseudonymousEditor, The Female Spectator]
-
A.
directedUnderPseudonym
Indicates that a work was directed by a person using a pseudonym rather than their real name.
-
B.
pseudonymousProducerIs
chosen
Indicates that one entity is the pseudonymous producer (creator operating under a pseudonym) of another entity.
-
C.
pseudonymousAttribution
Indicates that an action, work, or statement is attributed to an entity using a pseudonym rather than their real identity.
-
D.
pseudonymCoinedBy
Indicates that a particular pseudonym was created or invented by a specific agent or source.
-
E.
publishedAnonymously
Indicates that a work was made public without revealing the identity of its creator or author.
- 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_69e77e83c8ec8190bf52fcdac4838984 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fc0e881081909ac33b3e42e82471 |
completed | May 2, 2026, 1:28 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 8:59 p.m.