Triple
T38345868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chardjuy |
E1041536
|
entity |
| Predicate | historicalPeriodOfNameUse |
P3656
|
FINISHED |
| Object | Soviet era |
—
|
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: Soviet era | Statement: [Chardjuy, historicalPeriodOfNameUse, Soviet era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalPeriodOfNameUse Context triple: [Chardjuy, historicalPeriodOfNameUse, Soviet era]
-
A.
historicalNameUsedIn
Indicates that a historical or former name was used to refer to a particular entity in some context.
-
B.
historicalPeriodOfUse
chosen
Indicates the time period during which something was in active use or commonly utilized.
-
C.
historicalEraOfNaming
Indicates the historical era or time period during which an entity received its name.
-
D.
historicalNameUntil
Indicates that an entity bore a particular historical name up to a specified point in time, after which that name was no longer used.
-
E.
eraNameUsedInHistoriography
Indicates that a particular historical era name is used within historiographical writing or scholarship to refer to a period or context.
- 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_69f76e2ad95481908c920c0e5c1c3e26 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a022c5269888190944314074aedfe73 |
completed | May 11, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_6a02286020308190b238183f7ba2065f |
completed | May 11, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:30 p.m.