Triple
T31199992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A. J. Quinnell |
E795444
|
entity |
| Predicate | hasPenNameFor |
P3799
|
FINISHED |
| Object | Philip Nicholson |
—
|
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: Philip Nicholson | Statement: [A. J. Quinnell, hasPenNameFor, Philip Nicholson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPenNameFor Context triple: [A. J. Quinnell, hasPenNameFor, Philip Nicholson]
-
A.
pseudonymCoinedBy
Indicates that a particular pseudonym was created or invented by a specific agent or source.
-
B.
replacedByPenName
Indicates that an entity’s original name has been superseded or substituted by a pen name used by that entity.
-
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.
pseudonymPurpose
Indicates that a pseudonym is used for a specific purpose, function, or intended use in a given context.
- 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_69f224d8c6608190b7882466521f62be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: April 29, 2026, 9:09 p.m.