Triple
T22264115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishop's Palace, Barchester |
E550303
|
entity |
| Predicate | firstPublishedInContext |
P47750
|
FINISHED |
| Object | 1850s |
—
|
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: 1850s | Statement: [Bishop's Palace, Barchester, firstPublishedInContext, 1850s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPublishedInContext Context triple: [Bishop's Palace, Barchester, firstPublishedInContext, 1850s]
-
A.
firstPublicationContext
Indicates the original context or setting (such as venue, medium, or circumstance) in which something was first published.
-
B.
firstPublicationIn
chosen
Indicates the initial venue, medium, or context in which a work was first published.
-
C.
firstPublishedWith
Indicates that an entity was initially published together with another specified entity, sharing the same first publication event.
-
D.
firstDraftPublishedIn
Indicates that the first draft of a work was published or made publicly available in a specified venue, medium, or publication.
-
E.
initialPublication
Indicates the relationship in which a work is first formally published or made publicly available.
- 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_69e11e42adb8819087714772ea606709 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f141ba5c9481909e24067133918ae2 |
completed | April 28, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69e72fe1e0cc8190bd13cff2a0846225 |
completed | April 21, 2026, 8:05 a.m. |
Created at: April 16, 2026, 8:39 p.m.