Triple
T20320493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henrician Reformation |
E492193
|
entity |
| Predicate | hasApproximateStartTimeDescription |
P48368
|
FINISHED |
| Object | early 1530s |
—
|
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: early 1530s | Statement: [Henrician Reformation, hasApproximateStartTimeDescription, early 1530s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateStartTimeDescription Context triple: [Henrician Reformation, hasApproximateStartTimeDescription, early 1530s]
-
A.
timeStartApprox
chosen
Indicates that the associated event or state begins at an approximate, rather than exact, point in time.
-
B.
hasApproximateDuration
Indicates that one entity has a duration that is estimated or not exact, typically expressed as an approximate length of time.
-
C.
hasApproximatePublicationStart
Indicates that an entity is associated with an estimated or imprecise starting date for its publication.
-
D.
hasTimeStart
Indicates that an event, process, or state begins at a specific point in time.
-
E.
hasApproximateEnd
Indicates that an entity’s end point, time, or boundary is known only approximately rather than precisely.
- 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6778b8b648190b80badaf15be2599 |
completed | April 20, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69e5762655ac8190a8cc48a29fa2c0c4 |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:20 a.m.