Triple
T5943333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Novodevichy Convent |
E132218
|
entity |
| Predicate | significantBuildingPeriod |
P22153
|
FINISHED |
| Object | 16th 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: 16th century | Statement: [Novodevichy Convent, significantBuildingPeriod, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantBuildingPeriod Context triple: [Novodevichy Convent, significantBuildingPeriod, 16th century]
-
A.
historicalPeriodOfSignificance
Indicates the time period during which an entity is considered to have had its most important or influential historical impact.
-
B.
significantBuilding
Indicates that a building holds notable importance, prominence, or special status within a particular context (e.g., historical, cultural, architectural, or functional).
-
C.
eraOfMajorConstruction
chosen
Indicates the time period during which the primary or most significant phase of construction for an entity took place.
-
D.
locatedInHistoricPeriod
Indicates that an entity exists, occurs, or is situated within a specific historic period or era.
-
E.
occupationPeriod
Indicates the time span during which an entity holds or held a particular occupation or role.
- 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_69c00869d3308190af89b2453e0f7546 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c03ee10b308190afe38b904ae7c5f7 |
completed | March 22, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69c0335806788190b6488ca8b73f7a63 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4:01 p.m.