Triple
T29510424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tschaikovsky Piano Concerto No. 2 |
E748632
|
entity |
| Predicate | revisionPeriod |
P167440
|
FINISHED |
| Object | 1970s |
—
|
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: 1970s | Statement: [Tschaikovsky Piano Concerto No. 2, revisionPeriod, 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revisionPeriod Context triple: [Tschaikovsky Piano Concerto No. 2, revisionPeriod, 1970s]
-
A.
majorRevisionPeriod
Indicates the time span during which substantial or significant changes are made to something, such as a document, plan, or project.
-
B.
recurringEra
Indicates a relationship where a particular era or time period repeats or recurs, rather than occurring only once.
-
C.
periodOfRevival
Indicates a time span during which something that had declined or been inactive experiences renewed growth, activity, or prominence.
-
D.
periodicallyRevisedAt
Indicates that something is updated or revised at recurring, regular points in time.
-
E.
archivesPeriod
Indicates that one entity serves as an archival record or repository for materials, information, or events associated with a specified time period.
- F. None of above. chosen
Provenance (4 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_69f0bd461c208190bec20bbf24e02cc5 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66c5eea08819084483ef268d36b28 |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 4:31 p.m.