Triple
T28776318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northanger Abbey (estate) |
E726542
|
entity |
| Predicate | earlierCompositionDateOfWorkItAppearsIn |
P134575
|
FINISHED |
| Object | circa 1798–1799 |
—
|
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: circa 1798–1799 | Statement: [Northanger Abbey (estate), earlierCompositionDateOfWorkItAppearsIn, circa 1798–1799]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlierCompositionDateOfWorkItAppearsIn Context triple: [Northanger Abbey (estate), earlierCompositionDateOfWorkItAppearsIn, circa 1798–1799]
-
A.
dateOfComposition
Indicates the calendar date or time period when a particular work was created or composed.
-
B.
hasUnknownExactDateOfComposition
Indicates that the precise date when a work was composed is not known.
-
C.
dateOfCompositionHypothesis
chosen
Indicates a hypothesized or uncertain date when something (such as a work or document) was composed.
-
D.
periodOfOriginOfSourceWork
Indicates the historical time period during which the original source work was created or first came into existence.
-
E.
approximateDateOfFirstPrinting
Indicates the estimated or uncertain date when an item was first printed.
- 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_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 28, 2026, 6:17 a.m.