Triple
T26249642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mrs. Weston |
E656544
|
entity |
| Predicate | authorBirthplaceOfWorkAuthor |
P90944
|
FINISHED |
| Object | Steventon, Hampshire |
—
|
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: Steventon, Hampshire | Statement: [Mrs. Weston, authorBirthplaceOfWorkAuthor, Steventon, Hampshire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorBirthplaceOfWorkAuthor Context triple: [Mrs. Weston, authorBirthplaceOfWorkAuthor, Steventon, Hampshire]
-
A.
creatorLivedIn
Indicates that the person who created a work resided in a particular place for some period of time.
-
B.
creatorPlaceOfBirth
chosen
Indicates that the place specified is the location where the creator of an entity was born.
-
C.
brandBirthplaceOf
Indicates the place where a brand was originally founded or created.
-
D.
authorOfWorkAbout
Indicates that one entity is the author or creator of a work whose subject or content is about another entity.
-
E.
isBirthplaceRelatedTo
Indicates that there is a relationship between an entity and a birthplace, such as being born there or otherwise closely associated with that place of birth.
- 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_69ee5b4d25ac819086acb51184602576 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 26, 2026, 9:06 p.m.