Triple
T28780084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Memorials of Jane Austen |
E726650
|
entity |
| Predicate | authorRelationToJaneAusten |
P157650
|
FINISHED |
| Object | nephew |
—
|
LITERAL FINISHED |
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: nephew | Statement: [Memorials of Jane Austen, authorRelationToJaneAusten, nephew]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorRelationToJaneAusten Context triple: [Memorials of Jane Austen, authorRelationToJaneAusten, nephew]
-
A.
George AustenRole
Indicates that a specified role or position is held or performed by George Austen.
-
B.
subjectRelationToAuthor
chosen
Indicates the relationship or connection that the subject has to the author.
-
C.
famousWriterAssociated
Indicates a relationship where a well-known or renowned writer is connected or linked to a particular entity (such as a work, place, event, or organization).
-
D.
editorRelationshipToAuthors
Indicates the editorial role or connection an editor has in relation to the authors of a work.
-
E.
hasAuthorRelationship
Indicates a relationship where one entity serves as the author or creator of another entity (such as a work, document, or resource).
- 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: April 28, 2026, 6:19 a.m.