Triple
T8569756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petrograd Conservatory |
E202896
|
entity |
| Predicate | historicalPeriodOfName |
P39753
|
FINISHED |
| Object | early 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: early 20th century | Statement: [Petrograd Conservatory, historicalPeriodOfName, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalPeriodOfName Context triple: [Petrograd Conservatory, historicalPeriodOfName, early 20th century]
-
A.
historicalEraOfNaming
chosen
Indicates the historical era or time period during which an entity received its name.
-
B.
historicalNameType
Indicates that the relationship specifies the type or category of a historical name associated with an entity.
-
C.
regionHistoricalName
Indicates that a region has been known by a particular historical name during some past period.
-
D.
etymologyPeriod
Indicates the historical time period during which a word’s form or meaning, as described by its etymology, was in use or originated.
-
E.
formerNamePeriodStart
Indicates the date or time point when an entity began using a former name that is being recorded.
- 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_69ca8327b0a881908606ff860713964d |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbea4091f48190b5174d7a5cfd2bd8 |
completed | March 31, 2026, 3:37 p.m. |
| PD | Predicate disambiguation | batch_69cbd11856048190a1ce4b83a38f6965 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:21 p.m.