Triple
T33631932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nicholas Cornwell |
E861586
|
entity |
| Predicate | hasPseudonymForm |
P3799
|
FINISHED |
| Object | Nick Harkaway |
—
|
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: Nick Harkaway | Statement: [Nicholas Cornwell, hasPseudonymForm, Nick Harkaway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPseudonymForm Context triple: [Nicholas Cornwell, hasPseudonymForm, Nick Harkaway]
-
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.
revealedAsPseudonymIn
Indicates that one identity or name is disclosed or recognized as a pseudonym within a particular context, work, or source.
-
C.
pseudonymCoinedBy
Indicates that a particular pseudonym was created or invented by a specific agent or source.
-
D.
addresseePseudonym
Indicates that the referenced name is a pseudonym used for the addressee in the context of the described communication or interaction.
-
E.
coAppearsWithPseudonym
Indicates that an entity appears together with another entity that is identified or referenced by a pseudonym in the same context or source.
- 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_69f34981c54c81909b33c3fa2208a52d |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:41 a.m.