Triple
T30084916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kondratiev waves |
E764576
|
entity |
| Predicate | timeScaleComparedToBusinessCycle |
P168814
|
FINISHED |
| Object | longer |
—
|
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: longer | Statement: [Kondratiev waves, timeScaleComparedToBusinessCycle, longer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeScaleComparedToBusinessCycle Context triple: [Kondratiev waves, timeScaleComparedToBusinessCycle, longer]
-
A.
timeScaleCategory
Indicates the classification of an event or process based on the temporal scale or duration over which it occurs.
-
B.
timeScaleType
Indicates the type or category of temporal scaling applied to an event, process, or measurement (e.g., real-time, accelerated, aggregated).
-
C.
timeScaleUnit
Indicates the unit of temporal measurement (such as seconds, minutes, or hours) used to express a given time scale.
-
D.
timeScaleOfChange
Indicates the characteristic rate or temporal scale over which a change, process, or transition occurs.
-
E.
timeScaleStandard
Indicates the standard or convention used to define, measure, or interpret the time scale associated with an event or process.
- F. None of above. chosen
Provenance (4 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_69f67d6b85488190a14499b6bb2c9241 |
completed | May 2, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676f73c3481909f01fa69851b7298 |
completed | May 2, 2026, 10:13 p.m. |
Created at: April 29, 2026, 7:03 p.m.