Triple
T23946089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harpsichord |
E602916
|
entity |
| Predicate | experiencedRevivalInCentury |
P132499
|
FINISHED |
| Object | 20th century |
—
|
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: 20th century | Statement: [Harpsichord, experiencedRevivalInCentury, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: experiencedRevivalInCentury Context triple: [Harpsichord, experiencedRevivalInCentury, 20th century]
-
A.
hadResurgenceInCentury
chosen
Indicates that something experienced a renewed increase in activity, popularity, or significance during a specified century.
-
B.
experiencedRapidGrowthInCentury
Indicates that the entity underwent a significant and swift increase or expansion during the specified century.
-
C.
reestablishedInCentury
Indicates that an entity, previously established and then discontinued or disrupted, was re-founded or restored during a specified century.
-
D.
coveredSinceCentury
Indicates that one entity has been covered, coated, or kept under coverage continuously starting from a specified century.
-
E.
reacquiredInCentury
Indicates that an entity was reacquired during a specified century.
- 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_69e2953e4924819093f1c24c03476b42 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d02dd0cc8190b32eb86bdfe0bf9a |
completed | April 29, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:13 p.m.