Triple
T30084917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kondratiev waves |
E764576
|
entity |
| Predicate | originCountryOfTheory |
P49307
|
FINISHED |
| Object | Soviet Union |
—
|
NE NERFINISHED |
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 Union | Statement: [Kondratiev waves, originCountryOfTheory, Soviet Union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originCountryOfTheory Context triple: [Kondratiev waves, originCountryOfTheory, Soviet Union]
-
A.
countryOfEponym
Indicates that the related entity is named after something (an eponym) originating from or associated with a particular country.
-
B.
authorPrimaryCountryOfActivity
Indicates the main country in which an author predominantly conducts or conducted their professional or creative activities.
-
C.
countryOfNotableWork
Indicates the country with which a notable work is primarily associated, such as where it was created, set, or gained its significance.
-
D.
historicalOriginCountry
chosen
Indicates the country from which something originally came or first emerged in a historical context.
-
E.
speciesOrigin
Indicates the place, environment, or source from which a species originally arose or evolved.
- 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_69f22473c0fc8190a926a8051b3b378b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a00119d821c8190874786391b27ef23 |
completed | May 10, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_6a001143fb6881909ac0ae8bfea04351 |
completed | May 10, 2026, 5:01 a.m. |
Created at: April 29, 2026, 7:03 p.m.