Triple
T34850037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New-England Courant |
E1004574
|
entity |
| Predicate | hasPseudonymousContributor |
P56608
|
FINISHED |
| Object | Silence Dogood |
—
|
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: Silence Dogood | Statement: [New-England Courant, hasPseudonymousContributor, Silence Dogood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPseudonymousContributor Context triple: [New-England Courant, hasPseudonymousContributor, Silence Dogood]
-
A.
pseudonymousAttribution
Indicates that an action, work, or statement is attributed to an entity using a pseudonym rather than their real identity.
-
B.
pseudonymousProducerIs
chosen
Indicates that one entity is the pseudonymous producer (creator operating under a pseudonym) of another entity.
-
C.
coAppearsWithPseudonym
Indicates that an entity appears together with another entity that is identified or referenced by a pseudonym in the same context or source.
-
D.
usedPseudonymWith
Indicates that one entity employed a pseudonym or alias when interacting or being associated with another entity.
-
E.
hasAuthorRealName
Indicates that an entity (such as a work or pseudonym) is associated with the actual, legal name of its 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_69f76dba76f0819090643cba102c41ec |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782f4f10081908f97f6d0d2dbeec7 |
completed | May 3, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69f780ff71cc8190a67e71076fbad81a |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.