Triple
T11683482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joan Foster |
E277677
|
entity |
| Predicate | usesPseudonym |
P3799
|
FINISHED |
| Object | for her gothic romances |
—
|
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: for her gothic romances | Statement: [Joan Foster, usesPseudonym, for her gothic romances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPseudonym Context triple: [Joan Foster, usesPseudonym, for her gothic romances]
-
A.
usedPseudonym
chosen
Indicates that an entity performed an action or participated in a context under a name that was not their real or primary identity.
-
B.
pseudonymousAttribution
Indicates that an action, work, or statement is attributed to an entity using a pseudonym rather than their real identity.
-
C.
pseudonymCoinedBy
Indicates that a particular pseudonym was created or invented by a specific agent or source.
-
D.
pseudonymousProducerIs
Indicates that one entity is the pseudonymous producer (creator operating under a pseudonym) of another entity.
-
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_69d6aafe02d881909900d54ad7d4af84 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a462bb2881909238107d34c0a28d |
completed | April 10, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69d88a77e6e88190b7519100bde76575 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.