Triple
T20923707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stradivarius violin |
E515280
|
entity |
| Predicate | goldenPeriodApproxYears |
P35440
|
FINISHED |
| Object | 1700–1720 |
—
|
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: 1700–1720 | Statement: [Stradivarius violin, goldenPeriodApproxYears, 1700–1720]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goldenPeriodApproxYears Context triple: [Stradivarius violin, goldenPeriodApproxYears, 1700–1720]
-
A.
goldenAgeApproxEnd
Indicates the approximate time or period when a golden age or peak era comes to an end.
-
B.
timePeriodOfMajorExpansion
Indicates the time span during which the referenced entity underwent its most significant growth or expansion.
-
C.
legendaryPeriod
Indicates a time span associated with legends or mythic events rather than strictly historical chronology.
-
D.
historicalPeriodOfGreatestUse
Indicates the time period during which something was used most intensively or prevalently.
-
E.
approximateClassicalPeriod
chosen
Indicates that one entity corresponds to, or falls within, the approximate time span of another entity’s classical historical or cultural period.
- 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_69e0b4fb431c8190b9d40e6a72f0cc87 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6f6504c30819084e8cabab98d08f7 |
completed | April 21, 2026, 4 a.m. |
| PD | Predicate disambiguation | batch_69e5c9af1fe08190953366a466950140 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:49 p.m.