Triple
T34999688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tommy Poyser |
E1009635
|
entity |
| Predicate | workAuthorRealName |
P119633
|
FINISHED |
| Object | Mary Ann Evans |
—
|
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: Mary Ann Evans | Statement: [Tommy Poyser, workAuthorRealName, Mary Ann Evans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workAuthorRealName Context triple: [Tommy Poyser, workAuthorRealName, Mary Ann Evans]
-
A.
authorRealNameOfCreator
chosen
Indicates that a person’s real, legal, or birth name is the true identity behind a creator who may be known by a pseudonym or handle.
-
B.
alsoKnownAsRealAuthor
Indicates that an entity is an alternative or alias name identifying the same individual who is the actual (real) author of a work.
-
C.
workAuthorIs
Indicates that a specific person or entity is the author or creator of a particular work.
-
D.
literarySourceAuthorRealName
Indicates that the real (legal or birth) name of an author is the source of a given literary work or pseudonymous authorship.
-
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_69f76dcb716881909f75e4fd60ab2284 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.