Triple
T15563700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maastricht |
E371060
|
entity |
| Predicate | importancePeriod |
P4928
|
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: [Maastricht, importancePeriod, early modern period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: importancePeriod Context triple: [Maastricht, importancePeriod, early modern period]
-
A.
timePeriodOfMajorImportance
Indicates that a particular time period holds significant importance or prominence within a given context or domain.
-
B.
historicalPeriodOfSignificance
chosen
Indicates the time period during which an entity is considered to have had its most important or influential historical impact.
-
C.
peakImportance
Indicates that something reaches or represents the highest level of importance within a given context or timeframe.
-
D.
chronologicalSignificance
Indicates that one entity holds importance or relevance specifically due to its position, order, or timing within a chronological sequence relative to another.
-
E.
dateSignificance
Indicates the specific importance, meaning, or notable role that a particular date holds within a given context or relationship.
- 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_69d85cc6cf40819091f4a5facee1ebe6 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04ddc66448190948280fb0c8d390c |
completed | April 16, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_69deda7e6e748190b29ccce23298afef |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:10 a.m.