Triple
T24536186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CSKA Moscow |
E606955
|
entity |
| Predicate | historicalDominancePeriod |
P5898
|
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: [CSKA Moscow, historicalDominancePeriod, Soviet era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalDominancePeriod Context triple: [CSKA Moscow, historicalDominancePeriod, Soviet era]
-
A.
timePeriodOfDominance
chosen
Indicates the span of time during which an entity held dominance, control, or prevailing influence over another entity or context.
-
B.
historicallyDominantIn
Indicates that one entity has held a position of prevailing power, influence, or control over another entity or within a particular domain during a past historical period.
-
C.
occupationPeriod
Indicates the time span during which an entity holds or held a particular occupation or role.
-
D.
historicalEraOfSuccess
Indicates that an entity achieved notable success or prominence during a specified historical era.
-
E.
historicalPeriodOfGreatestUse
Indicates the time period during which something was used most intensively or prevalently.
- 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_69e2c4c90c848190b23c4303620dcaaf |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b0ca8081908d931aec560eae56 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:26 a.m.