Triple
T14136473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Estates of Hesse-Kassel |
E350307
|
entity |
| Predicate | existedInTimePeriod |
P97182
|
FINISHED |
| Object | early modern period |
—
|
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 modern period | Statement: [Estates of Hesse-Kassel, existedInTimePeriod, early modern period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: existedInTimePeriod Context triple: [Estates of Hesse-Kassel, existedInTimePeriod, early modern period]
-
A.
appearsInTimePeriod
chosen
Indicates that an entity is present, active, or occurs within a specified time period.
-
B.
isSetInTimePeriod
Indicates that an event, story, or situation takes place within a specified time period.
-
C.
occurredBetween
Indicates that an event or action took place within the time interval defined by two temporal boundaries.
-
D.
wasInForceDuring
Indicates that a rule, law, agreement, or other normative provision was legally valid and operative throughout a specified time period.
-
E.
existedUntil
Indicates that an entity continued to exist up to, but not necessarily beyond, a specified time or event.
- 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_69d827865f608190b311820428ae027b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de610fb86c81909eb26bf9c13696ca |
completed | April 14, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69de05b5e7a08190a16be9ad8b92b80c |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 12:18 a.m.