Triple
T12448878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edict of Restitution |
E297475
|
entity |
| Predicate | coveredPeriod |
P93275
|
FINISHED |
| Object | since 1552 |
—
|
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: since 1552 | Statement: [Edict of Restitution, coveredPeriod, since 1552]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coveredPeriod Context triple: [Edict of Restitution, coveredPeriod, since 1552]
-
A.
coversPeriodStart
Indicates that the time span or coverage of one entity begins at, or includes, the specified starting point in time of another entity or period.
-
B.
timePeriodCoveredTo
Indicates the span or duration of time that is encompassed, addressed, or relevant to a given subject or entity.
-
C.
agingPeriod
Indicates the length of time something is allowed or intended to mature or age before reaching its final or usable state.
-
D.
coveredSince
chosen
Indicates that one entity has been under the protection, applicability, or effect of another entity continuously starting from a specified point in time.
-
E.
focusPeriod
Indicates the specific time span during which attention, activity, or analysis is concentrated on something.
- 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_69d6ada166c48190b902972cd2408fa3 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95151e7348190a1d4953a8b416a13 |
completed | April 10, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69d94d3c27a08190a0237200203e476d |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:56 p.m.