Triple
T31152802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frederic Manning |
E794123
|
entity |
| Predicate | pseudonymUsedFor |
P3799
|
FINISHED |
| Object | Her Privates We |
—
|
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: Her Privates We | Statement: [Frederic Manning, pseudonymUsedFor, Her Privates We]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pseudonymUsedFor Context triple: [Frederic Manning, pseudonymUsedFor, Her Privates We]
-
A.
pseudonymCoinedBy
Indicates that a particular pseudonym was created or invented by a specific agent or source.
-
B.
revealedAsPseudonymIn
Indicates that one identity or name is disclosed or recognized as a pseudonym within a particular context, work, or source.
-
C.
pseudonymInspiredBy
Indicates that a pseudonym was chosen or created based on, or in homage to, another name, person, work, or concept.
-
D.
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.
-
E.
firstPublishedUnderPseudonym
Indicates that a work’s initial publication occurred under a pseudonym rather than the creator’s real name.
- 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_69f224d41bb48190a5621cd1485e3a30 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:06 p.m.