Triple
T8771111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 71-619 |
E208462
|
entity |
| Predicate | hasDesignEra |
P14116
|
FINISHED |
| Object | late Soviet period |
—
|
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: late Soviet period | Statement: [71-619, hasDesignEra, late Soviet period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDesignEra Context triple: [71-619, hasDesignEra, late Soviet period]
-
A.
hasDesignPeriod
chosen
Indicates that something was created, planned, or developed during a specified historical or stylistic design period.
-
B.
designedInCentury
Indicates that something was created or planned during a specific century.
-
C.
hasDesignOrigin
Indicates that one entity is the source, inspiration, or original model from which the design of another entity is derived.
-
D.
wasDevelopedInPeriod
Indicates that something was created, produced, or brought into existence during a specified time period.
-
E.
appliesToEra
Indicates that something is relevant, valid, or in effect during a particular historical or temporal era.
- 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_69ca835edb4481909b4aafb616dc5eb7 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5f2b08f881909f3d4fab2eda1d67 |
completed | March 31, 2026, 11:56 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1aff3881908be6a9cbc9f50461 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:41 p.m.