Triple
T30398937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medieval English Nunneries, c. 1275–1535 |
E773295
|
entity |
| Predicate | timeSpanEndsBefore |
P170762
|
FINISHED |
| Object | English Reformation |
—
|
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: English Reformation | Statement: [Medieval English Nunneries, c. 1275–1535, timeSpanEndsBefore, English Reformation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeSpanEndsBefore Context triple: [Medieval English Nunneries, c. 1275–1535, timeSpanEndsBefore, English Reformation]
-
A.
timeSpanIncludes
Indicates that one time span fully contains or covers the entire duration of another time span.
-
B.
earlierMPEndDate
Indicates that the end date of one Member of Parliament’s term occurs earlier in time than the end date of another Member of Parliament’s term.
-
C.
timeIntervalEndDefined
Indicates that the end point of a time interval is explicitly specified or determined.
-
D.
endDateInBand
Indicates that the end date of an event or interval falls within a specified date range or band.
-
E.
hasTemporalEnd
Indicates that an event, state, or process concludes or terminates at a specific point or interval in time.
- F. None of above. chosen
Provenance (4 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f695f9fe7c819084322bf6cdc70a13 |
completed | May 3, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f695385a2881908cc28ef97fffc867 |
completed | May 3, 2026, 12:22 a.m. |
Created at: April 29, 2026, 8:03 p.m.