Triple
T18337217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Foxe's Book of Martyrs |
E439302
|
entity |
| Predicate | statusInPeriod |
P123846
|
FINISHED |
| Object | quasi-official Protestant history in 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: quasi-official Protestant history in England | Statement: [Foxe's Book of Martyrs, statusInPeriod, quasi-official Protestant history in England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInPeriod Context triple: [Foxe's Book of Martyrs, statusInPeriod, quasi-official Protestant history in England]
-
A.
statusPeriod
Indicates the time interval during which a particular status or condition is in effect.
-
B.
statusAtTime
Indicates that an entity has a particular status or condition at a specified point in time.
-
C.
isSetInTimePeriod
Indicates that an event, story, or situation takes place within a specified time period.
-
D.
appliedDuringPeriod
chosen
Indicates that an action, condition, or status was in effect throughout a specified time period.
-
E.
statusIncludes
Indicates that one entity’s status set contains or encompasses the status (or statuses) of another entity.
- 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_69d8b9175fec8190af865699b4e64d8c |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50ece387881909a5da0aa4370489c |
completed | April 19, 2026, 5:20 p.m. |
| PD | Predicate disambiguation | batch_69e44fe91bc08190906518e1b120fcf0 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:37 a.m.