Triple
T32476125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Declaration of Egregious Popish Impostures |
E829979
|
entity |
| Predicate | settingOfEventsDescribed |
P130017
|
FINISHED |
| Object | late 16th-century England |
—
|
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: late 16th-century England | Statement: [A Declaration of Egregious Popish Impostures, settingOfEventsDescribed, late 16th-century England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingOfEventsDescribed Context triple: [A Declaration of Egregious Popish Impostures, settingOfEventsDescribed, late 16th-century England]
-
A.
basedOnEventsDescribedIn
Indicates that something is derived from, inspired by, or constructed using the events described in another source.
-
B.
storySettingEvent
chosen
Indicates that an event takes place within, or helps define, the setting or background context of a story.
-
C.
partOfSeriesOfEvents
Indicates that an event is one element within a larger, ordered sequence of related events.
-
D.
storylineEvent
Indicates that one event occurs as a distinct step or component within a larger narrative or storyline.
-
E.
settingOfLifeEvents
Indicates the location or environment in which significant life events of an entity take place.
- 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_69f3491ff3b48190b50a7fa00bb05b1f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 1, 2026, 12:58 a.m.